Cbg based transmission in multiple pdsch scheduling

ABSTRACT

There is disclosed a method of operating a receiving radio node in a wireless communication network. The method includes communicating utilising data signaling based on a received control information message, the control information message scheduling multiple occurrences of data signaling, wherein communicating is based on extracting a code block group (CBG) setup for communicating based on the received control information message and/or a CBG configuration. The disclosure also pertains to related devices and methods.

TECHNICAL FIELD

This disclosure pertains to wireless communication technology, inparticular for high frequencies.

BACKGROUND

For future wireless communication systems, use of higher frequencies isconsidered, which allows large bandwidths to be used for communication.However, use of such higher frequencies brings new problems, for exampleregarding physical properties and timing. Ubiquitous or almostubiquitous use of beamforming, with often comparatively small beams, mayprovide additional complications that need to be addressed.

SUMMARY

It is an object of this disclosure to provide improved approaches ofhandling wireless communication, in particular of data signaling. Theapproaches are particularly suitable for millimeter wave communication,in particular for radio carrier frequencies around and/or above 52.6GHz, which may be considered high radio frequencies (high frequency)and/or millimeter waves. The carrier frequency/ies may be between 52.6and 140 GHz, e.g. with a lower border between 52.6, 55, 60, 71 GHzand/or a higher border between 71, 72, 90, 114, 140 GHz or higher, inparticular between 55 and 90 GHz, or between 60 and 72 GHz; however,higher frequencies may be considered. The carrier frequency may inparticular refer to a center frequency or maximum frequency of thecarrier. The radio nodes and/or network described herein may operate inwideband, e.g. with a carrier bandwidth of 1 GHz or more, or 2 GHz ormore, or even larger, e.g. up to 8 GHz; the scheduled or allocatedbandwidth may be the carrier bandwidth, or be smaller, e.g. depending onchannel and/or procedure. In some cases, operation may be based on anOFDM waveform or a SC-FDM waveform (e.g., downlink and/or uplink), inparticular a FDF-SC-FDM-based waveform. However, operation based on asingle carrier waveform, e.g. SC-FDE (which may be pulse-shaped orFrequency Domain Filtered, e.g. based on modulation scheme and/or MCS),may be considered for downlink and/or uplink. In general, differentwaveforms may be used for different communication directions.Communicating using or utilising a carrier and/or beam may correspond tooperating using or utilising the carrier and/or beam, and/or maycomprise transmitting on the carrier and/or beam and/or receiving on thecarrier and/or beam.

The approaches are particularly advantageously implemented in a 5^(th)or 6th Generation (5G) telecommunication network or 5G radio accesstechnology or network (RAT/RAN), in particular according to 3GPP (3^(rd)Generation Partnership Project, a standardisation organization). Asuitable RAN may in particular be a RAN according to NR, for examplerelease 15 or later, or LTE Evolution. However, the approaches may alsobe used with other RAT, for example future 5.5G or 6G systems or IEEEbased systems.

There is disclosed a method of operating a receiving radio node in awireless communication network. The method comprises communicatingutilising data signaling based on a received control informationmessage, the control information message scheduling multiple occurrencesof data signaling. Communicating is based on extracting a code blockgroup (CBG) setup for communicating based on the received controlinformation message and/or a CBG configuration. Alternatively, oradditionally, the method may comprise one or more actions as describedherein with regard to a wireless device or UE or receiving radio node.

A receiving radio node for a wireless communication network isdescribed. The receiving radio node is adapted for communicatingutilising data signaling based on a received control informationmessage. The control information message schedules multiple occurrencesof data signaling. Communicating is based on extracting a code blockgroup (CBG) setup for communicating based on the received controlinformation message and/or a CBG configuration. Alternatively, oradditionally, the receiving radio node may be adapted for performing oneor more actions as described herein with regard to a wireless device orUE or receiving radio node.

There is also considered a method of operating a signaling radio node ina wireless communication network. The method comprises communicating,with a receiving radio node, utilising data signaling, Communicating isaccording to a code block group (CBG) setup indicated to the receivingradio node with a control information message scheduling multipleoccurrences of data signaling and/or a CBG configuration. Alternatively,or additionally, the method may comprise one or more actions asdescribed herein with regard to a network node or gNB or signaling radionode.

A signaling radio node for a wireless communication network is proposed.The signaling radio node is adapted for communicating, with a receivingradio node, utilising data signaling. The communicating is according toa code block group (CBG) setup indicated to the receiving radio nodewith a control information message scheduling multiple occurrences ofdata signaling and/or a CBG configuration. Alternatively, oradditionally, the signaling radio node may be adapted to perform one ormore actions as described herein with regard to a network node or gNB orsignaling radio node.

A code block group setup may indicate one or more parameters forhandling CBGs, e.g. for HARQ feedback or HARQ format. It may for examplecomprise and/or indicate transmission information (e.g., CBGTI) and/orflush information (CBGFI), for one or more data signaling occurrences,and/or a number of scheduled occurrences. Communicating may comprisetransmitting data signaling or feedback signaling (e.g., HARQinformation feedback). Transmitting feedback signaling may be based onreceiving the data signaling, e.g. as subject signaling, and/orreceiving the control information message. A HARQ codebook, which mayrepresent HARQ information signaling or feedback, may be based on thecode block group setup. A CBG configuration may indicate a format forthe data signaling, in particular for one or more occurrences, e.g.indicating which and/or how many CBG to be used, and/or how to providefeedback for the occurrence, e.g. for one or more CBGs. Each datasignaling occurrence may be represented by transmission of a data blocklike a transport block, which may comprise one or more CBGs, e.g.according to and/or in line with a CBG configuration. A signaling radionode may operate (e.g., communicate) according to a set and/orconfiguration, e.g. such that signaling it transmits conforms to thesetup and/or configuration and/or such that it assumes signaling itreceives conforms to the setup and/or configuration.

Approaches described herein allow handling of multiple occurrences ofdata signaling, which may be scheduled with (e.g., exactly and/or asingle) one control information message, e.g. one DCI message. Themultiple occurrences may pertain to the same communication direction,e.g. uplink or downlink or sidelink. The control information message maybe a scheduling assignment (e.g., scheduling the data signaling forreception by the receiving radio node) or a scheduling grant (e.g.,scheduling the data signaling for transmission by the receiving radionode). The control information message may be transmitted by thesignaling radio node. The CBG configuration may be pre-defined, and/orconfigured or configurable, e.g. by the signaling radio node and/or withhigher layer signaling, e.g. RRC signaling or RLC layer signaling or MAClayer signaling.

Extracting a CBG setup may comprise determining the CBG setup, e.g.based on information in the control information message and/or theconfiguration. In particular, the CBG setup may be determined based on anumber of schedulable or configured data signaling occurrence (e.g.,configured with the CBG configuration), and/or the number and/or size ofbit fields in the control information message, in particular bit fieldspertaining to a CBG, like CBGTI and/or CBGTI and/or pertaining to newdata (e.g., NDI, New Data Indication) and/or retransmission (e.g.,indicating RV, Redundancy Version) and/or M and/or F. It may beconsidered that a configured number of data signaling occurrences (whichmay be a maximum number) may pertain to a single data signalingoccurrence being scheduled with the control information message; formultiple occurrences scheduled with the control information message, thenumber of scheduled occurrences and/or the maximum number of scheduledor schedulable occurrences may be smaller, e.g. depending on the CBGconfiguration. The CBG setup may be determined based implicitly assumingCBG setup information based on the control information message and/orCBG configuration. The CBG setup may indicate different CBG setups fordifferent data signaling occurrences and/or acknowledgement signalinglike HARQ feedback pertaining thereto; in particular, the CBG setup mayindicate that for some occurrences (one or more) and/or transportblocks, HARQ feedback pertain to and/or is only for a transport blockand/or consists of one bit, e.g. one bit for one transport block, andfor some (one or more), HARQ feedback pertains to and/or is for one ormore CBGs of a transport block (and potentially for the transportblock), and/or comprises more than one bit, e.g. one each for a CBGand/or the transport block as a whole.

It may be considered that the data signaling may be on a physical uplinkdata channel or a physical downlink data channel, e.g. PUSCH or PDSCH.

It may be considered that the multiple occurrences of data signaling maybe associated to different transmission resources. Each occurrence maypertain to at least one different transmission resource. A transmissionresource may pertain to and/or comprise a frequency domain resourceand/or a time domain resource and/or a code resource and/or a layerand/or antenna port; resources may be distinguishable by associatedcoding (e.g., a cover code) and/or cyclic shift as cycling code and/or asignaling sequence, e.g. associated DM-RS (different/shifted DM-RS maybe used for different resources and/or occurrences). Each data signalingoccurrence may pertain to and/or represent a different transmission,e.g. on PUSCH or PDSCH or PSSCH, and/or to a different acknowledgementprocess, e.g. associated to a different HARQ ID. Different occurrencesmay be associated to the same carrier, or to different carriers.

The signaling radio node may in general comprise, and/or be adapted toutilise, processing circuitry and/or radio circuitry, in particular atransmitter and/or transceiver and/or receiver, to process (e.g.,trigger and/or schedule) and/or transmit reference signaling and/or forreceiving signaling indicative of the beam switching time. The signalingradio node (also referred to transmitting radio node) may in particularbe a network node or base station, and/or a network radio node; it maybe implemented as an IAB or relay node. However, in some cases, e.g. asidelink scenario, it may be a wireless device. In general, signalingradio node may comprise and/or be adapted for transmission diversity,and/or may be connected or connectable to, and/or comprise, antennacircuitry and/or two or more independently operable or controllableantenna arrays or arrangements and/or transmitter circuitries and/orantenna circuitries, and/or may be adapted to use (e.g., simultaneously)a plurality of antenna ports (e.g., for transmitting synchronisationsignaling, in particular first and second synchronisation signaling),e.g. controlling transmission using the antenna array/s. The signalingradio node may comprise multiple components and/or transmitters and/orTRPs (and/or be connected or connectable thereto) and/or be adapted tocontrol transmission from such. Any combination of units and/or devicesable to control transmission on an air interface and/or in radio asdescribed herein may be considered a signaling radio node.

The approaches are particularly advantageously implemented in a 5^(th)Generation (5G) telecommunication network or 5G radio access technologyor network (RAT/RAN), in particular according to 3GPP (3^(rd) GenerationPartnership Project, a standardisation organization). A suitable RAN mayin particular be a RAN according to NR, for example release 15 or later,or LTE Evolution. However, the approaches may also be used with otherRAT, for example future 5.5G or 6G systems or IEEE based systems. It maybe considered that the RAN is operating in an unlicensed frequency band(or carrier or part thereof) and/or based on a LBT procedure to access(for transmission) the frequency band (or carrier or part thereof), forexample in a License Assisted Access (LAA) operation mode and/or in thecontext of NR-U (NR unlicensed).

There is also described a program product comprising instructionscausing processing circuitry to control and/or perform a method asdescribed herein. Moreover, a carrier medium arrangement carrying and/orstoring a program product as described herein is considered. Aninformation system comprising, and/or connected or connectable, to aradio node and/or wireless device is also disclosed.

It may be considered that the data signaling represents one occurrenceof data signaling, e.g. covering a data block The data signaling may bepart of a longer data signaling sequence, which may cover, and/or beembedded in, and/or represent a data transmission (time) interval. Thedata transmission interval may comprise a plurality of data signalingoccurrences, each of which may carry, and/or be capable or configured orscheduled to carry, a different data block. The occurrences may bescheduled or configured jointly, e.g. with a scheduling grant orassignment, or separately, e.g. with multiple scheduling assignments. Adata transmission time and/or data signaling sequence may comprise atleast 2, at least 4, or at least 8 data signaling occurrences.

It may be considered that each data block (and/or code block and/or codeblock bundle and/or data signaling occurrence) may be associated to adifferent acknowledgement signaling process. Different processes may beassociated to different process IDs and/or data (sub-) streams and/ortransmission layers and/or buffers (e.g., for soft combining).

In general, it may be considered that a code block represents a part ofa data block and/or CBB. A part of a data block associated to anallocation unit may be a code block, or a different part (e.g., smalleror larger than one code block, and/or comprising parts of more than onecode block).

Communication may be based on TDD and/or FDD. Communicating may ingeneral comprise transmitting and/or receiving signaling, e.g. datasignaling. Communicating utilising or using data signaling may comprisetransmitting or receiving data signaling, e.g. data signaling beingtransmitted according to the code block distribution. A node beingconfigured for data signaling, e.g. receiving data signaling, may beconsidered to be set up with, and/or provided with a configuration orindication of a code block distribution, and/or provided with the codeblock distribution and/or associated mapping, and/or the associatedresource structure/s, e.g. with control signaling, e.g. physical layersignaling or higher layer signaling, in particular with schedulingassignment/s and/or grant/s and/or resource configuration using higherlayer signaling, e.g. RRC signaling configuring resources for datasignaling (and/or indicating the CB distribution, e.g. indicating a Codeblock bundle size, and/or CB and/or BS as discussed herein)

A feedback or receiving radio node in general may be configured orconfigurable, e.g. by a network or a radio node, in particular asignaling radio node. The data signaling and/or code block bundle/sand/or signaling resource structure or structures may be configured withcontrol information or control signaling, e.g. with physical layersignaling, e.g. on a physical control channel like PDCCH or PSCCH (forexample, it may be scheduled, e.g. with one or more schedulingassignments or scheduling grants), and/or with higher layer signaling,e.g. RRC layer or MAC layer signaling, which may for example be mappedto a data channel, like PDSCH or PSSCH or similar. The indicationsignaling and/or indication resource structure may be configured withcontrol information or control signaling, e.g. with physical layersignaling, e.g. on a physical control channel like PDCCH or PSCCH (forexample, it may be scheduled or triggered, e.g. with one or morescheduling assignments or scheduling grants), and/or with higher layersignaling, e.g. RRC layer or MAC layer signaling, which may for examplebe mapped to a data channel, like PDSCH or PSSCH or similar.

A receiving radio node may comprise, and/or be adapted to utilise,processing circuitry and/or radio circuitry, in particular a receiverand/or transceiver and/or transmitter, for receiving the subjectsignaling like data signaling like data signaling and/or controlssignaling, and/or for receiving control signaling associated to subjectsignaling, and/or for higher layer processing, and/or for demodulatingand/or decoding the data and/or control and/or subject signaling, and/orfor determining and/or transmitting control signaling, e.g. feedbacksignaling like acknowledgment signaling, in particular HARQ feedback.The receiving radio node may be a network node like a base station orrelay node or a reception point or transmission and reception point, ormay be implemented as wireless device like a terminal or user equipment.A receiving radio node may generally be adapted to receive signalingfrom the signaling radio node, e.g. data signaling and/or controlsignaling, and/or subject signaling.

A signaling radio node may comprise, and/or be adapted to utilise,processing circuitry and/or radio circuitry, in particular a transmitterand/or receiver and/or transceiver, for transmitting the subjectsignaling like data signaling, and/or control signaling like one or morescheduling assignment/s associated to subject signaling and/orrepresenting subject signaling, and/or encoding and/or mapping codeblock/s and or CBGs to subject or data signaling, and/or for higherlayer processing and/or receiving and/or transmitting of controlsignaling. The signaling radio node may be a network node like a basestation or relay node or a reception point or transmission and receptionpoint, or may be implemented as wireless device like a terminal or userequipment. A signaling radio node may generally be adapted to transmitand/or receive signaling to and/or from the receiving radio node, e.g.data signaling and/or control signaling, in particular feedbacksignaling like HARQ feedback signaling and/or acknowledgement signaling.

Receiving data signaling may comprise and/or be based on decoding and/ordemodulating data signaling, e.g. based on a configuration and/orscheduling information. Data signaling may be configured and/orscheduled for transmission and/or reception, e.g. by the network or anetwork node, for example with physical layer signaling and/or higherlayer signaling. For example, a network node as signaling radio node mayconfigure and/or schedule data signaling to be received by a wirelessdevice, or as a receiving node, it may schedule or configure datasignaling to be transmitted by a wireless device. Receiving may be basedon the assumption that code blocks are mapped to allocation units asdescribed herein. Transmitting data signaling may be based on and/orcomprise, mapping information or data or corresponding bits to codeblocks and/or allocation units, e.g. based on a modulation scheme and/orscheduling and/or operating conditions. A network node may be adapted toschedule and/or configure data signaling.

There is also described a program product comprising instructionscausing processing circuitry to control and/or perform a method asdescribed herein. Moreover, a carrier medium arrangement carrying and/orstoring a program product as described herein is considered. Aninformation system comprising, and/or connected or connectable, to aradio node is also disclosed.

The data signaling may be associated to a data channel, and/or apriority level. Different data signalings may be associated to differentdata channels, or different priority levels, e.g. for URLLC or otherhigh priority signaling.

Transmission parameters may comprise in particular frequency resourcesand/or start (in time domain, e.g. in which allocation unit) and/ormodulation and/or coding (in particular, modulation and coding scheme)and/or code rate and/or beam parameters, e.g. pertaining to the beam inwhich the data signaling is transmitted) and/or MIMO parameter/s and/orparameter/s indicating an arrangement of code blocks of the datasignaling, and/or information regarding reception, e.g. antenna and/orbeams for reception, and/or information indicative of a beam pair to usefor transmission and/or reception.

A code block may in general represent bits of information (e.g., userdata and/or payload) and/or error coding, and/or may be represented by acorresponding bit sequence. A code block (e.g., its bits orrepresentation) may be mapped to one or more modulation symbolscontained in the one or more allocation units (e.g., depending onmodulation and/or coding scheme and/or bandwidth and/or waveform). Theallocation unit may in some cases contain reference signaling, e.g.phase tracking reference signaling, which may for example be included asa sequence, e.g. in a fixed and/or predefined and/or configured orconfigurable location (e.g. in time domain) of the allocation unit.Control information like header information and/or similar from higherlayers may be represented by the information bits of the code block. Ingeneral, a code block may be padded (e.g. with zeros or ones) to allowoccupying an allocation unit, e.g. if the code block size otherwise istoo small to fully occupy one allocation unit. Alternatively, paddingsignaling may be used, e.g. padding symbols associated to the allocationunit not completely filled by a code block and/or its error codedrepresentation. An error coded representation of a code block maycomprise bits representing the information of the code block and/orerror detection coding and/or error correction coding; the informationbits may be directly included, or transformed (e.g., when using polarcoding for FEC). A code block bundle (CBB) or code block group (CBG) maycomprise a plurality of code blocks; the code blocks in a CBB may beencoded separately.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are provided to illustrate concepts and approachesdescribed herein, and are not intended to limit their scope. Thedrawings comprise:

FIG. 1, showing an exemplary HARQ feedback scenario;

FIG. 2, showing a schematic flowchart for an exemplary operationscenario;

FIG. 3, showing a schematic flowchart for another exemplary operationscenario;

FIG. 4, showing an exemplary receiving radio node, implementable as awireless device; and

FIG. 5, showing an exemplary signaling radio node, implementable as anetwork node.

DETAILED DESCRIPTION

In this disclosure, reference may be made to symbols. A symbol in thiscontext may be considered an example of an allocation unit or blocksymbol, and these terms may be used interchangeably, e.g. for differentwaveforms. In the following, there are described, by way of example,some approaches in the context of NR technology. However, approaches maybe analogously applicable in other contexts.

Downlink control information may be representative of control signaling.In the 3GPP NR standard, downlink control information (DCI), which istransmitted in a physical downlink control channel (PDCCH), may be usedto indicate DL data related information, UL related information, powercontrol information, slot format indication, etc. There are differentformats of DCI associated with each of these control signals and the UEmay identify them based on different radio network temporary identifiers(RNTIs) and/or one or more signaling characteristics.

A UE may be configured by higher layer signaling to monitor for Das indifferent resources with different periodicities, etc. DCI formats 1_0,1_1, and 1_2 (which are examples of scheduling assignments) may be usedfor scheduling DL data (which may be a form of subject signaling) whichis sent in a physical downlink shard channel (PDSCH); these formats mayindicate and/or allocate and/or include time and frequency resources forDL transmission, and/or modulation and coding information, HARQ (hybridautomatic repeat request) information, etc.

In case of DL semi-persistent scheduling (SPS) and UL configured granttype 2, part of the scheduling including the periodicity is provided bya higher layer configuration, while the rest of scheduling informationsuch as time domain and frequency domain resource allocation, modulationand coding, etc, are provided by the DCI in PDCCH.

The time domain resources for the scheduled PDSCH or PUSCH may beindicated to the UE via a 4-bit time domain resource assignment (TDRA)field, which may be an example of a time resource indication. The TDRAfield value m of the DCI provides a row index m+1 to an time domainresource allocation table. An exemplary PDSCH time domain resourceallocation table is shown in Table 1. Each indexed row defines a slotoffset K₀, the start and length indicator SLIV, or equivalently thestart symbol S and the allocation length L, and the PDSCH mapping typeto be assumed in the PDSCH reception. Similarly, each row in the PUSCHtime domain resource allocation table defines a slot offset K₂, thestart and length indicator SLIV, or directly the start symbol S and theallocation length L, and the PUSCH mapping type.

TABLE 1 Exemplary PDSCH time domain resource allocation table PDSCH Rowmapping index K₀ S L type 1 0 2 12 Type A 2 0 2 10 Type A 3 0 2 9 Type A4 0 2 7 Type A 5 0 2 5 Type A 6 0 9 4 Type B 7 0 4 4 Type B 8 0 5 7 TypeB 9 0 5 2 Type B 10 0 9 2 Type B 11 0 12 2 Type B 12 0 1 13 Type A 13 01 6 Type A 14 0 2 4 Type A 15 0 4 7 Type B 16 0 8 4 Type B

In Rel-15 NR, a DCI can schedule one PDSCH or one PUSCH and, hence, eachrow of the PDSCH or PUSCH time domain resource allocation table containstime domain resource parameters for one PDSCH or one PUSCH. In Rel-16NR, the PUSCH time domain resource allocation table is enhanced suchthat each row can provide the start symbols and the allocation lengths,and the PUSCH mapping types for multiple consecutive PUSCH starting fromone slot offset K₂. An exemplary Rel-16 PUSCH time domain resourceallocation table with multiple PUSCH scheduling is shown in Table 2. Row1 can be used to schedule two consecutive PUSCHs both starting in OS #0with lengths 14 OSs and with the same mapping type A. Row 2 can be usedto schedule two consecutive PUSCHs with different lengths. Row 3 can beused to schedule three consecutive PUSCHs with different lengths anddifferent mapping types.

TABLE 2 Exemplary Rel-16 PUSCH time domain resource allocation tablewith multiple PUSCH scheduling PUSCH Row mapping index K₂ S L type 1 j0, 0 14, 14 Type A, Type A 2 j 0, 0 14, 12 Type A, Type A 3 j 0, 0, 214, 14, 10 Type A, Type A, Type B 4 j 0, 2 12, 10 Type A, Type B . . . .. . . . . . . . . . .

Uplink control information may be seen as a form of control signalingtransmitted by a receiving radio node like a UE or terminal. Uplinkcontrol information (UCI) may be control information sent by a UE to agNB. It may comprise and/or consist of

-   -   Acknowledgement information in the form of Hybrid-ARQ        acknowledgement (HARQ-ACK) which is a feedback information        corresponding to, and/or associated to, a (scheduled) downlink        transport block, indicating for example whether the transport        block reception is successful or not,    -   Measurement information like Channel state information (CSI)        related to downlink channel conditions, which provides a gNB        with channel-related information useful for DL scheduling,        including information for multi-antenna and beamforming schemes,        and/or    -   Scheduling request (SR), which indicates a need of UL resources        for UL data transmission.

UCI is typically transmitted on physical uplink control channel (PUCCH).However, if a UE is transmitting data on a PUSCH with a valid PUSCHresource overlapping with PUCCH, UCI can be multiplexed with UL data andtransmitted on PUSCH instead, if the timeline requirements for UCImultiplexing is met.

A Physical Uplink Control Channel (PUCCH) may be used by a UE to atransmit feedback, which may include a HARQ-ACK feedback message,corresponding to the reception of DL data transmission (which may besubject signaling). It may also be used by the UE to send channel stateinformation (CSI) and/or to request for an uplink grant for transmittingUL data.

In NR, there exist multiple PUCCH formats supporting different UCIpayload sizes. PUCCH formats 0 and 1 support UCI up to 2 bits, whilePUCCH formats 2, 3, and 4 can support UCI of more than 2 bits. In termsof PUCCH transmission duration, PUCCH formats 0 and 2 are consideredshort PUCCH formats supporting PUCCH duration of 1 or 2 OFDM symbols,while PUCCH formats 1,3, and 4 are considered as long formats and cansupport PUCCH duration from 4 to 14 symbols.

The frequency/time resources for sending the HARQ-ACK informationcorresponding a PDSCH are indicated by PUCCH resource indicator (PRI)field and K₁ in the DCI which points to one of PUCCH resources that areconfigured by higher layers.

If the first symbol of PUCCH intended to carry the HARQ-ACK informationstarts no earlier than at symbol L₁, where L₁ is defined as the earliestuplink symbol with its CP starting after T_(proc,1) after the end of thelast symbol of the PDSCH carrying the TB being acknowledged, then the UEshall provide a valid HARQ-ACK information, wherein T_(proc,1) is givenin the standard.

Otherwise, if the UE is not provided with a K₁ that allows for enoughprocessing time, the UE may not provide a valid HARQ-ACK correspondingto the scheduled PDSCH in the indicated PUCCH occasion. This case canhappen if the first symbol of PUCCH which carries the HARQ-ACKinformation starts earlier than T_(proc,1) after the end of the lastsymbol of the PDSCH carrying the TB being acknowledged.

NR defines 2 UE categories with respect to PDSCH decoding time Ni. Nidepends on the DMRS configuration, UE capability and the subcarrierspacing as shown in tables 3 and 4.

TABLE 3 PDSCH processing time for PDSCH processing capability 1 PDSCHdecoding time N₁ [symbols] dmrs-AdditionalPosition ≠ pos0dmrs-AdditionalPosition = pos0 in DMRS-DownlinkConfig in either of inDMRS-DownlinkConfig in both of dmrs-DownlinkForPDSCH-MappingTypeA,dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeBor μ dmrs-DownlinkForPDSCH-MappingTypeB if the higher layer parameter isnot configured 0 8 N_(1, 0) 1 10 13 2 17 20 3 20 24

TABLE 4 PDSCH processing time for PDSCH processing capability 2 PDSCHdecoding time N₁ [symbols] dmrs-AdditionalPosition = pos0 inDMRS-DownlinkConfig in both of dmrs-DownlinkForPDSCH-MappingTypeA, μdmrs-DownlinkForPDSCH-MappingTypeB 0 3   1 4.5 2 9 for frequency range 1

A procedure for receiving downlink transmission may comprise that the UEfirst monitors and decodes a PDCCH in slot n, which points to a subjecttransmission (DL data, on PDSCH) scheduled in slot n+K₀ slots (K₀ islarger than or equal to 0). The UE then decodes the data in thecorresponding PDSCH. Based on the outcome of the decoding, the UE sendsan acknowledgement of the correct decoding (ACK) or a negativeacknowledgement (NACK) to the gNB at time slot n+K₀+K₁ (in case of slotaggregation n+K₀ would be replaced by the slot where PDSCH ends). Bothof K₀ and K₁ are indicated in the DCI. The resources for sending theacknowledgement are indicated by PUCCH resource indicator (PRI) field inthe DCI which points to one of PUCCH resources that are configured byhigher layers.

Depending on DL/UL slot configurations, or whether carrier aggregation,or per code-block group (CBG) transmission used in the DL, the feedbackfor several PDSCHs may need to be multiplexed in one feedback. This isdone by constructing HARQ-ACK codebooks. In NR, the UE can be configuredto multiplex the A/N bits using a semi-static codebook or a dynamiccodebook.

FIG. 1 illustrates the timeline in a simple scenario with two PDSCHs andone feedback. In this example, there are a total of 4 PUCCH resourcesconfigured, and the PRI indicates PUCCH 2 to be used for HARQ feedback.FIG. 1 shows an example of a transmission timeline. The timing forsending HARQ feedback is determined based on both PDSCH transmissionslot with reference to PDCCH slot (K₀) and the PUCCH slot that containsHARQ feedback (K₁).

A UE may be configurable with a maximum of 4 PUCCH resource sets fortransmission of HARQ-ACK information. Each set is associated with arange of UCI payload bits including HARQ-ACK bits. The first set isalways associated to 1 or 2 HARQ-ACK bits and may include only PUCCHformat 0 or 1 or both. The range of payload values (minimum of maximumvalues) for other sets, if configured, is provided by configuration,except the maximum value for the last set where a default value is used,and the minimum value of the second set being 3. The first set caninclude a maximum of 32 PUCCH resources of PUCCH format 0 or 1. Othersets can include maximum 8 bits of format 2 or 3 or 4.

The UE may determine a slot for transmission of HARQ-ACK bits in a PUCCHcorresponding to PDSCHs scheduled or activated by DCI via K1 valueprovided by configuration or a field in the corresponding DCI. The UEforms a codebook from the HARQ-ACK bits with associated PUCCH in a sameslot via corresponding K1 values.

The UE determines a PUCCH resource set that the size of the codebook iswithin the corresponding range of payload values associated to that set.The UE determines a PUCCH resource in that set if the set is configuredwith maximum 8 PUCCH resources, by a field in the last DCI associated tothe corresponding PDSCHs. If the set is the first set and is configuredwith more than 8 resources, a PUCCH resource in that set is determinedby a field in the last DCI associated to the corresponding PDSCHs andimplicit rules based on the CCE (Control Channel Element, a resourcestructure in a CORESET or search space monitored for DCI).

A PUCCH resource for HARQ-ACK transmission can overlap in time withother PUCCH resources for CSI and/or SR transmissions as well as PUSCHtransmissions in a slot. In case of overlapping PUCCH and/or PUSCHresources, first the UE resolves overlapping between PUCCH resources, ifany, by determining a PUCCH resource carrying the total UCI (includingHARQ-ACK bits) such that the UCI multiplexing timeline requirements aremet. There might be partial or completely dropping of CSI bits, if any,to multiplex the UCI in the determined PUCCH resource. Then, the UEresolves overlapping between PUCCH and PUSCH resources, if any, bymultiplexing the UCI on the PUSCH resource if the timeline requirementsfor UCI multiplexing is met.

Type 1 or semi-static codebook consists of a bit sequence where eachelement contains the A/N bit from a possible allocation in a certainslot, carrier, or transport block (TB). When the UE is configured withCBG and/or time-domain resource allocation (TDRA) table with multipleentries, multiple bits are generated per slot and TB (see below). It isimportant to note that the codebook is derived regardless of the actualPDSCH scheduling. The size and format of the semi-static codebook ispreconfigured based on the mentioned parameters. The drawback ofsemi-static HARQ ACK codebook is that the size is fixed, and regardlessof whether there is a transmission or not a bit is reserved in thefeedback matrix. In the case that a UE has a TDRA table with multipletime-domain resource allocation entries configured, the table may bepruned (e.g., entries may be removed based on a specified algorithm) toderive a TDRA table that only contains non-overlapping time-domainallocations. One bit is then reserved in the HARQ CB for eachnon-overlapping entry (assuming a UE is capable of supporting receptionof multiple PDSCH in a slot).

In type 2 or dynamic HARQ codebook, an A/N bit is present in a codebookonly if there is a corresponding transmission scheduled. To avoid anyconfusion between the gNB and the UE on the number of PDSCHs that the UEhas to send a feedback for, a counter downlink assignment indicator(counter DAI or C-DAI) field exists in DL assignment, which indicates(e.g., using a modulo operation) accumulative number of {serving cell,PDCCH occasion} pairs in which a PDSCH is scheduled to a UE up to thecurrent PDCCH. In addition to that, there is another field called totalDAI (T-DAI) when carrier aggregation is configured, which when presentindicates the total number of {serving cell, PDCCH occasion} up to (andincluding) all PDCCHs across all serving cells of the current PDCCHmonitoring occasion. The timing for sending HARQ feedback is determinedbased on both PDSCH transmission slot with reference to PDCCH slot (K₀)and the PUCCH slot that contains HARQ feedback (K₁).

An enhanced dynamic codebook or enhanced Type-2 codebook based on Type 2codebook is introduced to enable retransmission of the HARQ feedbackcorresponding to the used HARQ processes. If, for any reason, thescheduled codebook (representing the HARQ feedback) was not receivedfrom the UE, the retransmission of the feedback can be requested by thegNB. A toggle bit, new feedback indicator (NFI), is added in the DCI toindicate whether the HARQ-ACK feedback from the UE was received by thegNB or not. If toggled, the UE assumes that the reported feedback wascorrectly received. Otherwise, if the gNB fails to receive the scheduledPUCCH, the UE is expected to retransmit the feedback. In the lattercase, the DAI (C/T-DAI) counting is not reset, instead the DAI areaccumulated within a PDSCH group until NFI for the PDSCH group istoggled.

As the triggering of additional HARQ feedback reporting occurs withambiguous timing relation to the associated PDSCHs, PDSCH grouping isintroduced. A PDSCH group is defined as the PDSCH(s) for which theHARQ-ACK information is originally indicated to be carried in a samePUCCH. PDSCH grouping allows the gNB to explicitly indicate whichcodebook is missing. The group index is explicitly signaled in thescheduling DCI. If an enhanced dynamic codebook is configured, two PDSCHgroups are supported. Together with the group ID, the gNB signals arequest group ID which is a 1-bit field. By referring to the group Id(ID), request ID (RI), and the value of the NFI field in the DCI, the UEcan figure out if the next feedback occasion should include only initialtransmission or also retransmission of feedback corresponding toPDSCH(s) associated with the indicated group.

Similar to NR, the DAI value may also be included in the UL grantscheduling PUSCH. As an additional functionality, the gNB can indicatethe DAI value for each group separately in the UL grant to resolve anypossible ambiguity at the UE side.

A one-shot (Type-3) HARQ codebook may be used. The UE may be configuredto monitor for a feedback request of a HARQ-ACK codebook containing allDL HARQ processes. The feedback can be requested in DL DCI format 1_1.In response to the trigger, the UE reports the HARQ-ACK feedback for all(e.g., current) DL HARQ processes. The format of the feedback, eitherCBG-based HARQ-ACK or TB-based HARQ-ACK, can be configured to be part ofthe one-shot HARQ feedback for the component carriers.

Additionally, to resolve any possible ambiguity between the gNB and theUE that might be caused by possible mis-detection of PDCCH(s), the UEcan be configured to report the corresponding latest NDI value for alatest received PDSCH for that HARQ process along with the correspondingHARQ-ACK for the received PDSCH. From a gNB perspective, if the NDIvalue matches the last transmitted value, it indicates that the reportedHARQ-ACK feedback correctly corresponds to the HARQ process with pendingfeedback. Otherwise, the mismatch suggests that the UE is reporting anoutdated feedback.

Up to rel-16, the PDSCH can be scheduled using DCI 1_0, 1_1,2_1, allwhich schedule one PDSCH at a time. Multiple PDSCH scheduling, i.e., oneDL DCI schedules multiple PDSCHs, may be considered. A solution todynamically enable CBG based HARQ feedback for multiple PDSCH scheduling(with one scheduling assignment) is proposed.

The proposed approaches may enhance DL data scheduling DCI Formats tosupport CBG based HARQ feedback for multiple PDSCH scheduling.Specifically, approaches are provided to update DL DCI Formats todynamically indicate TB based or CBG based HARQ feedback in multiplePDSCH scheduling.

A CBG-based HARQ feedback solution is provided, and dynamic switchingbetween TB based and CBG based HARQ feedback in multiple PDSCHscheduling is facilitated.

Even though the variants below are explicitly referring to multiplePDSCH scheduling, they are equally equivalent to multiple PUSCHscheduling, where multiple PUSCH scheduling and PUSCH-CodeBlockGroupTransmission can be configured simultaneously.

According to following variants, a UE may be configured withPDSCH-CodeBlockGroupTransmission, which indicates CBG based transmissionis used and the maximum number of CBGs per TB (M). If the UE is notconfigured with PDSCH-CodeBlockGroupTransmission, it should may TB basedtransmission is used. A transport block (TB) may be considered anexample of a data block, a CBG may be an example of a sub block.

In one variant, a UE may be configured with maxNrofMultiplePDSCHs-r17and maxNrofMultiplePDSCHsWithCBG-r17, which respectively indicate themaximum number of PDSCHs scheduled by a single DCI (denoted as X) andmaximum number of PDSCHs scheduled by a single DCI and with CBGTI/CBGFIincluded (denoted as Y); this may be in context of multiple PDSCHscheduling (by one DCI) being enabled and/or configured.

In a DL DCI format that may schedule multiple PDSCHs, there are somefields that may be PDSCH specific, such as NDI (New Data Indicator) andRV (Redundancy Version). Assuming the number of bits for NDI and RV asN_(NDI) and N_(RV) respectively, the total number of bits for signalingNDI and RV in a multiple PDSCH scheduling DCI is (N_(NDI)+N_(RV))*X,where X is the higher layer configured maxNrofMultiplePDSCHs-r17.

If CBG based transmission should be used in conjunction with multiplePDSCH scheduling, for each CBG scheduled PDSCH, a CBGTI field of M bitsand a CBGFI field of F bit may be included into the schedulingassignment, where M may be the higher layer configuredmaxCodeBlockGroupsPerTransportBlock, and F may be 0 or 1, e.g.,depending on higher layer configured codeBlockGroupFlushIndicator.Hence, the total number of bits for signaling NDI, RV and CBGTI in amultiple PDSCH scheduling DCI with CBG base transmission is(N_(NDI)+N_(RV)+M+F)*Y, where Y is the higher layer configuredmaxNrofMultiplePDSCHsWithCBG-r17.

According to this variant, in a multiple PDSCH scheduling scenario, UEdetects a DCI Format 1_1 or other form of scheduling assignment. Thenumber of PDSCHs being scheduling (N) is obtained from reading the TDRAfield of the DCI, and the pre-configured higher layer PDSCH Time DomainResource Allocation table (e.g.,pdsch-TimeDomainAllocationList-ForMultiPDSCH-r17). The UE may determinewhether CBGTI/CBGFI is included in the DCI per scheduled PDSCH accordingto the following procedure:

-   -   If CBG based transmission is not configured, UE should assume        CBGTI/CBGFI is not included for all scheduled PDSCHs;    -   Otherwise, if CBG based transmission is configured:        -   If N is larger than Y, UE should assume CBGTI/CBGFI is not            included for all scheduled PDSCHs;        -   Otherwise, i.e., Nis smaller or equal

to Y, UE should assume CBGTI/CBGFI is included for all scheduled PDSCHs.

This decision-making procedure is illustrated in the flowchart in FIG. 2Figure. FIG. 2 shows a flow chart for determinating whether CBGTI/CBGFIis included per scheduled PDSCH, according to a variant 1.

If the CBGTI for a scheduled PDSCH is not included in the DCI, the UEmay implicitly assume that all the CBGs for said PDSCH are included inthe transmitted PDSCH, e.g., the equivalent to indicating CBGTI is all“1”s.

If the CBGFI for a scheduled PDSCH is not included in the DCI, the UEmay implicitly assume that CBGFI for said PDSCH equals to “0”.

According to this variant, based on a maxNrofMultiplePDSCHs-r17configuration, the DCI may contain a fixed (N_(NDI)+N_(RV))*X bits to beshared between the information fields needed for multiple PDSCH and CBGscheduling. That is, the following inequation may be maintained:

(N_(NDI) + N_(RV))^(*)X >  = (N_(NDI) + N_(RV) + M + F)^(⋆)Y

The maximum number of PDSCHs with CBGTI/CBGFI included in the multiplescheduling DCI may be:

$Y = \left\lfloor \frac{\left( {N_{NDI} + N_{RV}} \right)*X}{N_{NDI} + N_{RV} + M + F} \right\rfloor$

where └x┘ is the floor function giving the largest integer no largerthan x.

The maximum number of PDSCHs scheduled by a single DCI and withCBGTI/CBGFI included (denoted as Y) can be derived by the gNB andexplicitly signaled to the UE by means of RRC configuration (e.g. thehigher layer configured maxNrofMultiplePDSCHsWithCBG-r17).Alternatively, the gNB may signal the maximum number of CBGs per TB (M)which is used by the UE to implicitly derive Y (e.g. using the equationsabove).

As an example, assume X=8, N_(NDI)=1, N_(RV)=1, M=4, F=0, Y should be nomore than 2.

As another example, assume X=8, N_(NDI)=1, N_(RV)=1, M=2, F=0, Y shouldbe no more than 4.

The UE may be configured accordingly.

The inequation equation may be generalized to consider other DCI fieldsdepending on whether or not CBG-based transmission is configured. Forexample, it may be assumed that the summation of the bit-widths of allDCI fields that are present when CBG-based transmission is notconfigured is donated by Z_(TB) and the summation of bit-widths of allDCI fields that are present when CBG-based transmission is configured isdonated by Z_(CBG).

The following inequation may be maintained (e.g., by configuring theUE/receiving radio node) accordingly:

Z_(TB) + (N_(NDI) + N_(RV))^(*)X >  = (N_(NDI) + N_(RV) + M + F)^(⋆)Y + Z_(CBG).

Certain fields can be disabled depending on whether or not CBG-basedtransmission is configured, and in such a situation, Z_(TB)≠Z_(CBG). Forexample, the gNB can configure absence of certain fields when CBG-basedtransmission is configured, for instance, ZP CSI-RS trigger, and/or SRSrequest, etc.

According to another variant, a multiple scheduling DCI can stillschedule up to X PDSCHs as pre-configured by higher layer, even when CBGbase transmission is also configured. In this case, CBGTI/CBGFI for thefirst (or last) Y PDSCHs are assumed to be included, while CBGTI/CBGFIfor the remaining PDSCHs are assumed to be not included. The gNB mayensure the following inequation to hold such that the total number ofbits for signaling NDI, RV, CBGTI and CBGFI does not increase comparedto the case when CBG based transmission is not configured:

(N_(NDI) + N_(RV))^(⋆)X >  = (N_(NDI) + N_(RV) + M + F)^(⋆)Y + (N_(NDI) + N_(RV))^(⋆)(N − Y)

According to this variant, UE may determine whether CBGTI/CBGFI isincluded in the DCI per scheduled PDSCH according to the followingprocedure

-   -   If CBG based transmission is not configured, the UE may assume        CBGTI/CBGFI is not included for all scheduled PDSCHs;    -   Otherwise, if CBG based transmission is configured:        -   If N is larger than Y, UE may assume CBGTI/CBGFI is included            for the first (or the last) Y PDSCHs, while not included for            the remaining PDSCHs;        -   Otherwise, i.e., N is smaller or equal to Y, UE may assume            CBGTI/CBGFI to be included for all scheduled PDSCHs.

This decision-making procedure is illustrated in the flowchart in FIG.3. FIG. 3 shows a flowchart for determinating whether CBGTI/CBGFI isincluded per scheduled PDSCH according to a variant 2

If the CBGTI for a scheduled PDSCH is not included in the DCI, the UEmay implicitly assume that all the CBGs for said PDSCH are included inthe transmitted PDSCH, equivalent to indicating CBGTI is all “1”s. Ifthe CBGFI for a scheduled PDSCH is not included in the DCI, the UE mayimplicitly assume that CBGFI for said PDSCH equals to “0”.

As an example, there may be assumed X=8, N_(NDI)=1, N_(RV)=1, M=4, F=0,Y=2. If the UE identifies from the DCI that N is 4, the UE may assumeCBG based transmission for the first 2 PDSCHs, and TB based transmissionfor the other 2 PDSCHs. If may be considered that either the first orthe last Y PDSCHs are indicated with CBGTI/CBGFI are specified in therelevant specification.

Alternatively, or additionally, the UE may determine either the first orthe last Y PDSCHs are indicated with CBGTI/CBGFI according to thefollowing procedure:

-   -   Among the fixed (N_(NDI)+N_(RV))*X bits, the first        (N_(NDI)+N_(RV))*N bits are used for NDI and RX;    -   the remaining bits (N_(NDI)+N_(RV))*(X−N) are allocated to        CBGTI/CBGFI for Y PDSCHs, where Y is derived as:

${Y = {\min\left( {N,\left\lfloor \frac{\left( {N_{NDI} + N_{RV}} \right)*\left( {X - N} \right)}{M + F} \right\rfloor} \right)}};$

-   -   If Y=N, all N scheduled PDSCHs are indicated with CBGTI/CBGFI;    -   Otherwise, the number of left-over bits is        (N_(NDI)+N_(RV))*(X−N)−(M+F)*Y;    -   If (N_(NDI)+N_(RV))*(X−N)−(M+F)*Y=0: UE should assume the first        (or last, as specified by the relevant specification) Y        scheduled PDSCHs are indicated with CBGTI/CBGFI, the remaining        (N-Y) scheduled PDSCHs are not;    -   If (N_(NDI)+N_(RV))*(X−N)−(M+F)*Y>0: use the i-th bit is used as        indicator where i=((N_(NDI)+N_(RV))*N+(M+F)*Y);    -   If i-th bit is 0: UE should assume the first Y scheduled PDSCHs        are indicated with CBGTI/CBGFI, the remaining (N−Y) scheduled        PDSCHs are not;    -   If i-th bit is 1: UE should assume the last Y scheduled PDSCHs        are indicated with CBGTI/CBGFI, the remaining (N−Y) scheduled        PDSCHs are not;

The reverse approach may be utilised analogously.

Alternatively, or additionally, if the UE is configured withPDSCH-CodeBlockGroupTransmission and multiple PDSCH scheduling, the UEmay prepare CBG-based HARQ-ACK feedback for all scheduled PDSCHsregardless of whether CBGTI or CBGFI fields of any of the scheduledPDSCHs are actually included in the DCI according the above DCIprocessing variants.

More alternatively, or additionally, if the UE is configured withPDSCH-CodeBlockGroupTransmission and multiple PDSCH scheduling, the UEmay prepare

-   -   CBG-based HARQ-ACK feedback for the scheduled PDSCHs with        CBGTI/CBGFI included in the DCI; and/or    -   TB-based HARQ-ACK feedback for the scheduled PDSCHs without        CBGTI/CBGFI included in the DCI, according the above DCI        processing variants.

FIG. 4 schematically shows a radio node, in particular a wireless deviceor terminal or a UE (User Equipment) or receiving radio node. Radio node10 comprises processing circuitry (which may also be referred to ascontrol circuitry) 20, which may comprise a controller connected to amemory. Any module of the radio node 10, e.g. a communicating module ordetermining module, may be implemented in and/or executable by, theprocessing circuitry 20, in particular as module in the controller.Radio node 10 also comprises radio circuitry 22 providing receiving andtransmitting or transceiving functionality (e.g., one or moretransmitters and/or receivers and/or transceivers), the radio circuitry22 being connected or connectable to the processing circuitry. Anantenna circuitry 24 of the radio node 10 is connected or connectable tothe radio circuitry 22 to collect or send and/or amplify signals. Radiocircuitry 22 and the processing circuitry 20 controlling it areconfigured for cellular communication with a network, e.g. a RAN asdescribed herein, and/or for sidelink communication (which may be withincoverage of the cellular network, or out of coverage; and/or may beconsidered non-cellular communication and/or be associated to anon-cellular wireless communication network). Radio node 10 maygenerally be adapted to carry out any of the methods of operating aradio node like terminal or UE disclosed herein; in particular, it maycomprise corresponding circuitry, e.g. processing circuitry, and/ormodules, e.g. software modules. It may be considered that the radio node10 comprises, and/or is connected or connectable, to a power supply.

FIG. 5 schematically show a radio node 100, which may in particular beimplemented as a network node 100 or signaling radio node, for examplean eNB or gNB or similar for NR. Radio node 100 comprises processingcircuitry (which may also be referred to as control circuitry) 120,which may comprise a controller connected to a memory. Any module, e.g.transmitting module and/or receiving module and/or configuring module ofthe node 100 may be implemented in and/or executable by the processingcircuitry 120. The processing circuitry 120 is connected to controlradio circuitry 122 of the node 100, which provides receiver andtransmitter and/or transceiver functionality (e.g., comprising one ormore transmitters and/or receivers and/or transceivers). An antennacircuitry 124 may be connected or connectable to radio circuitry 122 forsignal reception or transmittance and/or amplification. Node 100 may beadapted to carry out any of the methods for operating a radio node ornetwork node disclosed herein; in particular, it may comprisecorresponding circuitry, e.g. processing circuitry, and/or modules. Theantenna circuitry 124 may be connected to and/or comprise an antennaarray. The node 100, respectively its circuitry, may be adapted toperform any of the methods of operating a network node or a radio nodeas described herein; in particular, it may comprise correspondingcircuitry, e.g. processing circuitry, and/or modules. The radio node 100may generally comprise communication circuitry, e.g. for communicationwith another network node, like a radio node, and/or with a core networkand/or an internet or local net, in particular with an informationsystem, which may provide information and/or data to be transmitted to auser equipment.

In general, a clear channel assessment (CCA) procedure may comprisemonitoring and/or performing measurements on a frequency range and/orchannel and/or carrier and/or spectrum; in some cases a CCA proceduremay also be referred to as LBT procedure; e.g., if only one CCA isperformed for a LBT procedure. In particular, the CCA procedure maycomprise determining whether a channel or frequency range or spectrum orcarrier is occupied, for example based on one or more parameters, e.g.measured or monitored energy and/or power and/or signal strength and/orenergy density and/or power density or similar. A CCA procedure may beperformed and/or pertain to a specific time interval (also referred toas CCA duration), for example a measuring or monitoring interval overwhich measurement and/or monitoring is performed. The CCA procedure maybe performed and/or pertain to a specific frequency range (also referredto as CCA frequency range), for example a measurement and/or monitoringrange. The CCA frequency range may be part of and/or comprise thefrequency range and/or carrier and/or spectrum and/or channel to beaccessed (which may be referred to as access target frequency range, oraccess target in short; accessing in this context may be considered torefer to transmitting signaling on the range and/or carrier and/orspectrum). The CCA frequency range may be considered representative ofthe access target frequency range in terms of occupation status(occupied or non-occupied). A CCA procedure may indicate whether theaccess target is occupied or not, for example by comparing measurementresults with one or more threshold values. For example, if the measuredpower or energy over the CCA duration is lower than an occupancythreshold, the access target may be considered unoccupied; if it reachesor is higher than the threshold, it may be considered occupied. Adetermination as unoccupied may be considered a positive result; adetermination of occupied may be considered a negative result. AListen-Before-Talk procedure (LBT) may comprise one or more CCAprocedure in an LBT time interval, for example with the same durationand/or same condition or threshold for positive result, or withdifferent durations and/or different conditions or thresholds. An LBTprocedure may be considered positive if a threshold number of CCAs ofthe LBT procedure are positive, for example each or half, and/or aminimum consecutive in time are positive. A positive LBT and/or CCAprocedure may allow access to the access target for transmission, forexample to be accessed within an access time interval. Access(permission to transmit) may be valid for a channel occupation time(COT); the maximum time of access may be a maximum COT (M-COT). The timeof access may be referred to as transmission duration (which may be aslong as the M-COT or shorter). A radio node like a wireless device doesnot have to transmit the whole M-COT after successful CCA/LBT. It may beconsidered that part of the M-COT is passed on to another device, whichthen may transmit (using the rest of the M-COT), e.g. upon and/or basedon suitable control signaling; this may be particularly useful in acentralised system. For example, in centralised system, a base stationmay initiate an access, transmit DL signaling to a wireless devicescheduled for UL transmission such that the wireless device transmitswithin the M-COT after the DL transmission has ended, e.g. due tosuitable scheduling information. The device performing successful accessto start transmission at the beginning of a M-COT or COT may beconsidered the device initiating a COT or M-COT. Depending on whetherthere is a gap between transmissions of different device, one or moreCCA procedures (in particular, shorter in total than for initiation) mayhave to be performed by the device taking over transmission. If a LBTprocedure was unsuccessful, a device may be required to backoff (e.g.,not trying to access for a backoff time interval, which may bepredefined or random). Accessing and/or transmitting on an access targetfrequency range may comprise on the whole bandwidth of the frequencyrange, or on part of it, for example interleaved and/or in a contiguouspart and/or utilising frequency hopping, and/or may be based onallocated and/or scheduled and/or configured resources, for example intime domain (e.g., for a number of symbols or a time interval) and/orfrequency domain (e.g., as in terms of frequency subranges and/orsubcarriers and/or PRBs and/or groups of PRBs assigned for transmission,e.g. allocated or scheduled or configured).

Data signaling may be on a data channel, for example on a PDSCH orPSSCH, or on a dedicated data channel, e.g. for low latency and/or highreliability, e.g. a URLLC channel. Control signaling may be on a controlchannel, for example on a common control channel or a PDCCH or PDCCH,and/or comprise one or more DCI messages or SCI messages. Referencesignaling may be associated to control signaling and/or data signaling,e.g. DM-RS and/or PT-RS.

Communicating may comprise transmitting or receiving. It may beconsidered that communicating like transmitting signaling is based on aSC-FDM based waveform, and/or corresponds to a Frequency Domain Filtered(FDF) DFTS-OFDM waveform. However, the approaches may be applied to aSingle Carrier based waveform, e.g. a SC-FDM or SC-FDE-waveform, whichmay be pulse-shaped/FDF-based. It should be noted that SC-FDM may beconsidered DFT-spread OFDM, such that SC-FDM and DFTS-OFDM may be usedinterchangeably. Alternatively, or additionally, the signaling (e.g.,first signaling and/or second signaling) and/or beam/s (in particular,the first received beam and/or second received beam) may be based on awaveform with CP or comparable guard time. The received beam and thetransmission beam of the first beam pair may have the same (or similar)or different angular and/or spatial extensions; the received beam andthe transmission beam of the second beam pair may have the same (orsimilar) or different angular and/or spatial extensions. It may beconsidered that the received beam and/or transmission beam of the firstand/or second beam pair have angular extension of 20 degrees or less, or15 degrees or less, or 10 or 5 degrees or less, at least in one ofhorizontal or vertical direction, or both; different beams may havedifferent angular extensions. An extended guard interval or switchingprotection interval may have a duration corresponding to essentially orat least N CP (cyclic prefix) durations or equivalent duration, whereinN may be 2, or 3 or 4. An equivalent to a CP duration may represent theCP duration associated to signaling with CP (e.g., SC-FDM-based orOFDM-based) for a waveform without CP with the same or similar symboltime duration as the signaling with CP. Pulse-shaping (and/or performingFDF for) a modulation symbol and/or signaling, e.g. associated to afirst subcarrier or bandwidth, may comprise mapping the modulationsymbol (and/or the sample associated to it after FFT) to an associatedsecond subcarrier or part of the bandwidth, and/or applying a shapingoperation regarding the power and/or amplitude and/or phase of themodulation symbol on the first subcarrier and the second subcarrier,wherein the shaping operation may be according to a shaping function.Pulse-shaping signaling may comprise pulse-shaping one or more symbols;pulse-shaped signaling may in general comprise at least one pulse-shapedsymbol. Pulse-shaping may be performed based on a Nyquist-filter. It maybe considered that pulse-shaping is performed based on periodicallyextending a frequency distribution of modulation symbols (and/orassociated samples after FFT) over a first number of subcarrier to alarger, second number of subcarriers, wherein a subset of the firstnumber of subcarriers from one end of the frequency distribution isappended at the other end of the first number of subcarriers.

In some variants, communicating may be based on a numerology (which may,e.g., be represented by and/or correspond to and/or indicate asubcarrier spacing and/or symbol time length) and/or an SC-FDM basedwaveform (including a FDF-DFTS-FDM based waveform) or a single-carrierbased waveform. Whether to use pulse-shaping or FDF on a SC-FDM orSC-based waveform may depend on the modulation scheme (e.g., MCS) used.Such waveforms may utilise a cyclic prefix and/or benefit particularlyfrom the described approaches. Communicating may comprise and/or bebased on beamforming, e.g. transmission beamforming and/or receptionbeamforming, respectively. It may be considered that a beam is producedby performing analog beamforming to provide the beam, e.g. a beamcorresponding to a reference beam. Thus, signaling may be adapted, e.g.based on movement of the communication partner. A beam may for examplebe produced by performing analog beamforming to provide a beamcorresponding to a reference beam. This allows efficient postprocessingof a digitally formed beam, without requiring changes to a digitalbeamforming chain and/or without requiring changes to a standarddefining beam forming precoders. In general, a beam may be produced byhybrid beamforming, and/or by digital beamforming, e.g. based on aprecoder. This facilitates easy processing of beams, and/or limits thenumber of power amplifiers/ADC/DCA required for antenna arrangements. Itmay be considered that a beam is produced by hybrid beamforming, e.g. byanalog beamforming performed on a beam representation or beam formedbased on digital beamforming. Monitoring and/or performing cell searchmay be based on reception beamforming, e.g. analog or digital or hybridreception beamforming. The numerology may determine the length of asymbol time interval and/or the duration of a cyclic prefix. Theapproaches described herein are particularly suitable to SC-FDM, toensure orthogonality, in particular subcarrier orthogonality, incorresponding systems, but may be used for other waveforms.Communicating may comprise utilising a waveform with cyclic prefix. Thecyclic prefix may be based on a numerology, and may help keepingsignaling orthogonal. Communicating may comprise, and/or be based onperforming cell search, e.g. for a wireless device or terminal, or maycomprise transmitting cell identifying signaling and/or a selectionindication, based on which a radio node receiving the selectionindication may select a signaling bandwidth from a set of signalingbandwidths for performing cell search.

A beam or beam pair may in general be targeted at one radio node, or agroup of radio nodes and/or an area including one or more radio nodes.In many cases, a beam or beam pair may be receiver-specific (e.g.,UE-specific), such that only one radio node is served per beam/beampair. A beam pair switch or switch of received beam (e.g., by using adifferent reception beam) and/or transmission beam may be performed at aborder of a transmission timing structure, e.g. a slot border, or withina slot, for example between symbols Some tuning of radio circuitry, e.g.for receiving and/or transmitting, may be performed. Beam pair switchingmay comprise switching from a second received beam to a first receivedbeam, and/or from a second transmission beam to a first transmissionbeam. Switching may comprise inserting a guard period to cover retuningtime; however, circuitry may be adapted to switch sufficiently quicklyto essentially be instantaneous; this may in particular be the case whendigital reception beamforming is used to switch reception beams forswitching received beams.

A reference beam may be a beam comprising reference signaling, based onwhich for example a of beam signaling characteristics may be determined,e.g. measured and/or estimated. A signaling beam may comprise signalinglike control signaling and/or data signaling and/or reference signaling.A reference beam may be transmitted by a source or transmitting radionode, in which case one or more beam signaling characteristics may bereported to it from a receiver, e.g. a wireless device. However, in somecases it may be received by the radio node from another radio node orwireless device. In this case, one or more beam signalingcharacteristics may be determined by the radio node. A signaling beammay be a transmission beam, or a reception beam. A set of signalingcharacteristics may comprise a plurality of subsets of beam signalingcharacteristics, each subset pertaining to a different reference beam.Thus, a reference beam may be associated to different beam signalingcharacteristics.

A beam signaling characteristic, respectively a set of suchcharacteristics, may represent and/or indicate a signal strength and/orsignal quality of a beam and/or a delay characteristic and/or beassociated with received and/or measured signaling carried on a beam.Beam signaling characteristics and/or delay characteristics may inparticular pertain to, and/or indicate, a number and/or list and/ororder of beams with best (e.g., lowest mean delay and/or lowestspread/range) timing or delay spread, and/or of strongest and/or bestquality beams, e.g. with associated delay spread. A beam signalingcharacteristic may be based on measurement/s performed on referencesignaling carried on the reference beam it pertains to. Themeasurement/s may be performed by the radio node, or another node orwireless device. The use of reference signaling allows improved accuracyand/or gauging of the measurements. In some cases, a beam and/or beampair may be represented by a beam identity indication, e.g. a beam orbeam pair number. Such an indication may be represented by one or moresignaling sequences (e.g., a specific reference signaling sequences orsequences), which may be transmitted on the beam and/or beam pair,and/or a signaling characteristic and/or a resource/s used (e.g.,time/frequency and/or code) and/or a specific RNTI (e.g., used forscrambling a CRC for some messages or transmissions) and/or byinformation provided in signaling, e.g. control signaling and/or systemsignaling, on the beam and/or beam pair, e.g. encoded and/or provided inan information field or as information element in some form of messageof signaling, e.g. DCI and/or MAC and/or RRC signaling.

A reference beam may in general be one of a set of reference beams, thesecond set of reference beams being associated to the set of signalingbeams. The sets being associated may refer to at least one beam of thefirst set being associated and/or corresponding to the second set (orvice versa), e.g. being based on it, for example by having the sameanalog or digital beamforming parameters and/or precoder and/or the sameshape before analog beamforming, and/or being a modified form thereof,e.g. by performing additional analog beamforming. The set of signalingbeams may be referred to as a first set of beams, a set of correspondingreference beams may be referred to as second set of beams.

In some variants, a reference beam and/or reference beams and/orreference signaling may correspond to and/or carry random accesssignaling, e.g. a random access preamble. Such a reference beam orsignaling may be transmitted by another radio node. The signaling mayindicate which beam is used for transmitting. Alternatively, thereference beams may be beams receiving the random access signaling.Random access signaling may be used for initial connection to the radionode and/or a cell provided by the radio node, and/or for reconnection.Utilising random access signaling facilitates quick and early beamselection. The random access signaling may be on a random accesschannel, e.g. based on broadcast information provided by the radio node(the radio node performing the beam selection), e.g. withsynchronisation signaling (e.g., SSB block and/or associated thereto).The reference signaling may correspond to synchronisation signaling,e.g. transmitted by the radio node in a plurality of beams. Thecharacteristics may be reported on by a node receiving thesynchronisation signaling, e.g. in a random access process, e.g. a msg3for contention resolution, which may be transmitted on a physical uplinkshared channel based on a resource allocation provided by the radionode.

A delay characteristic (which may correspond to delay spreadinformation) and/or a measurement report may represent and/or indicateat least one of mean delay, and/or delay spread, and/or delaydistribution, and/or delay spread distribution, and/or delay spreadrange, and/or relative delay spread, and/or energy (or power)distribution, and/or impulse response to received signaling, and/or thepower delay profile of the received signals, and/or power delay profilerelated parameters of the received signal. A mean delay may representthe mean value and/or an averaged value of the delay spread, which maybe weighted or unweighted. A distribution may be distribution overtime/delay, e.g. of received power and/or energy of a signal. A rangemay indicate an interval of the delay spread distribution overtime/delay, which may cover a predetermined percentage of the delayspread respective received energy or power, e.g. 50% or more, 75% ormore, 90% or more, or 100%. A relative delay spread may indicate arelation to a threshold delay, e.g. of the mean delay, and/or a shiftrelative to an expected and/or configured timing, e.g. a timing at whichthe signaling would have been expected based on the scheduling, and/or arelation to a cyclic prefix duration (which may be considered on form ofa threshold). Energy distribution or power distribution may pertain tothe energy or power received over the time interval of the delay spread.A power delay profile may pertain to representations of the receivedsignals, or the received signals energy/power, across time/delay. Powerdelay profile related parameters may pertain to metrics computed fromthe power delay profile. Different values and forms of delay spreadinformation and/or report may be used, allowing a wide range ofcapabilities. The kind of information represented by a measurementreport may be predefined, or be configured or configurable, e.g. with ameasurement configuration and/or reference signaling configuration, inparticular with higher layer signaling like RRC or MAC signaling and/orphysical layer signaling like DCI signaling.

In general, different beam pair may differ in at least one beam; forexample, a beam pair using a first received beam and a firsttransmission beam may be considered to be different from a second beampair using the first received beam and a second transmission beam. Atransmission beam using no precoding and/or beamforming, for exampleusing the natural antenna profile, may be considered as a special formof transmission beam of a transmission beam pair. A beam may beindicated to a radio node by a transmitter with a beam indication and/ora configuration, which for example may indicate beam parameters and/ortime/frequency resources associated to the beam and/or a transmissionmode and/or antenna profile and/or antenna port and/or precoderassociated to the beam. Different beams may be provided with differentcontent, for example different received beams may carry differentsignaling; however, there may be considered cases in which differentbeams carry the same signaling, for example the same data signalingand/or reference signaling. The beams may be transmitted by the samenode and/or transmission point and/or antenna arrangement, or bydifferent nodes and/or transmission points and/or antenna arrangements.

Communicating utilising a beam pair or a beam may comprise receivingsignaling on a received beam (which may be a beam of a beam pair),and/or transmitting signaling on a beam, e.g. a beam of a beam pair. Thefollowing terms are to be interpreted from the point of view of thereferred radio node: a received beam may be a beam carrying signalingreceived by the radio node (for reception, the radio node may use areception beam, e.g. directed to the received beam, or benon-beamformed). A transmission beam may be a beam used by the radionode to transmit signaling. A beam pair may consist of a received beamand a transmission beam. The transmission beam and the received beam ofa beam pair may be associated to each and/or correspond to each other,e.g. such that signaling on the received beam and signaling on atransmission beam travel essentially the same path (but in oppositedirections), e.g. at least in a stationary or almost stationarycondition. It should be noted that the terms “first” and “second” do notnecessarily denote an order in time; a second signaling may be receivedand/or transmitted before, or in some cases simultaneous to, firstsignaling, or vice versa. The received beam and transmission beam of abeam pair may be on the same carrier or frequency range or bandwidthpart, e.g. in a TDD operation; however, variants with FDD may beconsidered as well. Different beam pairs may operate on the samefrequency ranges or carriers or bandwidth parts (e.g., such thattransmission beams operate on the same frequency range or carriers orbandwidth part, and received beams on the same frequency range orcarriers or bandwidth part (the transmission beam and received beams maybe on the same or different ranges or carriers or BWPs). Communicatingutilizing a first beam pair and/or first beam may be based on, and/orcomprise, switching from the second beam pair or second beam to thefirst beam pair or first beam for communicating. The switching may becontrolled by the network, for example a network node (which may be thesource or transmitter of the received beam of the first beam pair and/orsecond beam pair, or be associated thereto, for example associatedtransmission points or nodes in dual connectivity). Such controlling maycomprise transmitting control signaling, e.g. physical layer signalingand/or higher layer signaling. In some cases, the switching may beperformed by the radio node without additional control signaling, forexample based on measurements on signal quality and/or signal strengthof beam pairs (e.g., of first and second received beams), in particularthe first beam pair and/or the second beam pair. For example, it may beswitched to the first beam pair (or first beam) if the signal quality orsignal strength measured on the second beam pair (or second beam) isconsidered to be insufficient, and/or worse than correspondingmeasurements on the first beam pair indicate. Measurements performed ona beam pair (or beam) may in particular comprise measurements performedon a received beam of the beam pair. It may be considered that thetiming indication may be determined before switching from the secondbeam pair to the first beam pair for communicating. Thus, thesynchronization may be in place 8 and/or the timing indication may beavailable for synchronising) when starting communication utilizing thefirst beam pair or first beam. However, in some cases the timingindication may be determined after switching to the first beam pair orfirst beam. This may be in particular useful if first signaling isexpected to be received after the switching only, for example based on aperiodicity or scheduled timing of suitable reference signaling on thefirst beam pair, e.g. first received beam.

In some variants, reference signaling may be and/or comprise CSI-RS,e.g. transmitted by the network node. In other variants, the referencesignaling may be transmitted by a UE, e.g. to a network node or otherUE, in which case it may comprise and/or be Sounding ReferenceSignaling. Other, e.g. new, forms of reference signaling may beconsidered and/or used. In general, a modulation symbol of referencesignaling respectively a resource element carrying it may be associatedto a cyclic prefix.

Data signaling may be on a data channel, for example on a PDSCH orPSSCH, or on a dedicated data channel, e.g. for low latency and/or highreliability, e.g. a URLLC channel. Control signaling may be on a controlchannel, for example on a common control channel or a PDCCH or PSCCH,and/or comprise one or more DCI messages or SCI messages. Referencesignaling may be associated to control signaling and/or data signaling,e.g. DM-RS and/or PT-RS.

Reference signaling, for example, may comprise DM-RS and/or pilotsignaling and/or discovery signaling and/or synchronisation signalingand/or sounding signaling and/or phase tracking signaling and/orcell-specific reference signaling and/or user-specific signaling, inparticular CSI-RS. Reference signaling in general may be signaling withone or more signaling characteristics, in particular transmission powerand/or sequence of modulation symbols and/or resource distributionand/or phase distribution known to the receiver. Thus, the receiver canuse the reference signaling as a reference and/or for training and/orfor compensation. The receiver can be informed about the referencesignaling by the transmitter, e.g. being configured and/or signalingwith control signaling, in particular physical layer signaling and/orhigher layer signaling (e.g., DCI and/or RRC signaling), and/or maydetermine the corresponding information itself, e.g. a network nodeconfiguring a UE to transmit reference signaling. Reference signalingmay be signaling comprising one or more reference symbols and/orstructures. Reference signaling may be adapted for gauging and/orestimating and/or representing transmission conditions, e.g. channelconditions and/or transmission path conditions and/or channel (or signalor transmission) quality. It may be considered that the transmissioncharacteristics (e.g., signal strength and/or form and/or modulationand/or timing) of reference signaling are available for both transmitterand receiver of the signaling (e.g., due to being predefined and/orconfigured or configurable and/or being communicated). Different typesof reference signaling may be considered, e.g. pertaining to uplink,downlink or sidelink, cell-specific (in particular, cell-wide, e.g.,CRS) or device or user specific (addressed to a specific target or userequipment, e.g., CSI-RS), demodulation-related (e.g., DMRS) and/orsignal strength related, e.g. power-related or energy-related oramplitude-related (e.g., SRS or pilot signaling) and/or phase-related,etc.

References to specific resource structures like an allocation unitand/or block symbol and/or block symbol group and/or transmission timingstructure and/or symbol and/or slot and/or mini-slot and/or subcarrierand/or carrier may pertain to a specific numerology, which may bepredefined and/or configured or configurable. A transmission timingstructure may represent a time interval, which may cover one or moresymbols. Some examples of a transmission timing structure aretransmission time interval (TTI), subframe, slot and mini-slot. A slotmay comprise a predetermined, e.g. predefined and/or configured orconfigurable, number of symbols, e.g. 6 or 7, or 12 or 14. A mini-slotmay comprise a number of symbols (which may in particular beconfigurable or configured) smaller than the number of symbols of aslot, in particular 1, 2, 3 or 4, or more symbols, e.g. less symbolsthan symbols in a slot. A transmission timing structure may cover a timeinterval of a specific length, which may be dependent on symbol timelength and/or cyclic prefix used. A transmission timing structure maypertain to, and/or cover, a specific time interval in a time stream,e.g. synchronized for communication. Timing structures used and/orscheduled for transmission, e.g. slot and/or mini-slots, may bescheduled in relation to, and/or synchronized to, a timing structureprovided and/or defined by other transmission timing structures. Suchtransmission timing structures may define a timing grid, e.g., withsymbol time intervals within individual structures representing thesmallest timing units. Such a timing grid may for example be defined byslots or subframes (wherein in some cases, subframes may be consideredspecific variants of slots). A transmission timing structure may have aduration (length in time) determined based on the durations of itssymbols, possibly in addition to cyclic prefix/es used. The symbols of atransmission timing structure may have the same duration, or may in somevariants have different duration. The number of symbols in atransmission timing structure may be predefined and/or configured orconfigurable, and/or be dependent on numerology. The timing of amini-slot may generally be configured or configurable, in particular bythe network and/or a network node. The timing may be configurable tostart and/or end at any symbol of the transmission timing structure, inparticular one or more slots.

A transmission quality parameter may in general correspond to the numberR of retransmissions and/or number T of total transmissions, and/orcoding (e.g., number of coding bits, e.g. for error detection codingand/or error correction coding like FEC coding) and/or code rate and/orBLER and/or BER requirements and/or transmission power level (e.g.,minimum level and/or target level and/or base power level P0 and/ortransmission power control command, TPC, step size) and/or signalquality, e.g. SNR and/or SIR and/or SINR and/or power density and/orenergy density.

A buffer state report (or buffer status report, BSR) may compriseinformation representing the presence and/or size of data to betransmitted (e.g., available in one or more buffers, for exampleprovided by higher layers). The size may be indicated explicitly, and/orindexed to range/s of sizes, and/or may pertain to one or more differentchannel/s and/or acknowledgement processes and/or higher layers and/orchannel groups/s, e.g., one or more logical channel/s and/or transportchannel/s and/or groups thereof: The structure of a BSR may bepredefined and/or configurable of configured, e.g. to override and/oramend a predefined structure, for example with higher layer signaling,e.g. RRC signaling. There may be different forms of BSR with differentlevels of resolution and/or information, e.g. a more detailed long BSRand a less detailed short BSR. A short BSR may concatenate and/orcombine information of a long BSR, e.g. providing sums for dataavailable for one or more channels and/or or channels groups and/orbuffers, which might be represented individually in a long BSR; and/ormay index a less-detailed range scheme for data available or buffered. ABSR may be used in lieu of a scheduling request, e.g. by a network nodescheduling or allocating (uplink) resources for the transmitting radionode like a wireless device or UE or IAB node.

There is generally considered a program product comprising instructionsadapted for causing processing and/or control circuitry to carry outand/or control any method described herein, in particular when executedon the processing and/or control circuitry. Also, there is considered acarrier medium arrangement carrying and/or storing a program product asdescribed herein.

A carrier medium arrangement may comprise one or more carrier media.Generally, a carrier medium may be accessible and/or readable and/orreceivable by processing or control circuitry. Storing data and/or aprogram product and/or code may be seen as part of carrying data and/ora program product and/or code. A carrier medium generally may comprise aguiding/transporting medium and/or a storage medium. Aguiding/transporting medium may be adapted to carry and/or carry and/orstore signals, in particular electromagnetic signals and/or electricalsignals and/or magnetic signals and/or optical signals. A carriermedium, in particular a guiding/transporting medium, may be adapted toguide such signals to carry them. A carrier medium, in particular aguiding/transporting medium, may comprise the electromagnetic field,e.g. radio waves or microwaves, and/or optically transmissive material,e.g. glass fiber, and/or cable. A storage medium may comprise at leastone of a memory, which may be volatile or non-volatile, a buffer, acache, an optical disc, magnetic memory, flash memory, etc.

A system comprising one or more radio nodes as described herein, inparticular a network node and a user equipment, is described. The systemmay be a wireless communication system, and/or provide and/or representa radio access network.

Moreover, there may be generally considered a method of operating aninformation system, the method comprising providing information.Alternatively, or additionally, an information system adapted forproviding information may be considered. Providing information maycomprise providing information for, and/or to, a target system, whichmay comprise and/or be implemented as radio access network and/or aradio node, in particular a network node or user equipment or terminal.Providing information may comprise transferring and/or streaming and/orsending and/or passing on the information, and/or offering theinformation for such and/or for download, and/or triggering suchproviding, e.g. by triggering a different system or node to streamand/or transfer and/or send and/or pass on the information. Theinformation system may comprise, and/or be connected or connectable to,a target, for example via one or more intermediate systems, e.g. a corenetwork and/or internet and/or private or local network. Information maybe provided utilising and/or via such intermediate system/s. Providinginformation may be for radio transmission and/or for transmission via anair interface and/or utilising a RAN or radio node as described herein.Connecting the information system to a target, and/or providinginformation, may be based on a target indication, and/or adaptive to atarget indication. A target indication may indicate the target, and/orone or more parameters of transmission pertaining to the target and/orthe paths or connections over which the information is provided to thetarget. Such parameter/s may in particular pertain to the air interfaceand/or radio access network and/or radio node and/or network node.Example parameters may indicate for example type and/or nature of thetarget, and/or transmission capacity (e.g., data rate) and/or latencyand/or reliability and/or cost, respectively one or more estimatesthereof. The target indication may be provided by the target, ordetermined by the information system, e.g. based on information receivedfrom the target and/or historical information, and/or be provided by auser, for example a user operating the target or a device incommunication with the target, e.g. via the RAN and/or air interface.For example, a user may indicate on a user equipment communicating withthe information system that information is to be provided via a RAN,e.g. by selecting from a selection provided by the information system,for example on a user application or user interface, which may be a webinterface. An information system may comprise one or more informationnodes. An information node may generally comprise processing circuitryand/or communication circuitry. In particular, an information systemand/or an information node may be implemented as a computer and/or acomputer arrangement, e.g. a host computer or host computer arrangementand/or server or server arrangement. In some variants, an interactionserver (e.g., web server) of the information system may provide a userinterface, and based on user input may trigger transmitting and/orstreaming information provision to the user (and/or the target) fromanother server, which may be connected or connectable to the interactionserver and/or be part of the information system or be connected orconnectable thereto. The information may be any kind of data, inparticular data intended for a user of for use at a terminal, e.g. videodata and/or audio data and/or location data and/or interactive dataand/or game-related data and/or environmental data and/or technical dataand/or traffic data and/or vehicular data and/or circumstantial dataand/or operational data. The information provided by the informationsystem may be mapped to, and/or mappable to, and/or be intended formapping to, communication or data signaling and/or one or more datachannels as described herein (which may be signaling or channel/s of anair interface and/or used within a RAN and/or for radio transmission).It may be considered that the information is formatted based on thetarget indication and/or target, e.g. regarding data amount and/or datarate and/or data structure and/or timing, which in particular may bepertaining to a mapping to communication or data signaling and/or a datachannel. Mapping information to data signaling and/or data channel/s maybe considered to refer to using the signaling/channel/s to carry thedata, e.g. on higher layers of communication, with thesignaling/channel/s underlying the transmission. A target indicationgenerally may comprise different components, which may have differentsources, and/or which may indicate different characteristics of thetarget and/or communication path/s thereto. A format of information maybe specifically selected, e.g. from a set of different formats, forinformation to be transmitted on an air interface and/or by a RAN asdescribed herein. This may be particularly pertinent since an airinterface may be limited in terms of capacity and/or of predictability,and/or potentially be cost sensitive. The format may be selected to beadapted to the transmission indication, which may in particular indicatethat a RAN or radio node as described herein is in the path (which maybe the indicated and/or planned and/or expected path) of informationbetween the target and the information system. A (communication) path ofinformation may represent the interface/s (e.g., air and/or cableinterfaces) and/or the intermediate system/s (if any), between theinformation system and/or the node providing or transferring theinformation, and the target, over which the information is, or is to be,passed on. A path may be (at least partly) undetermined when a targetindication is provided, and/or the information is provided/transferredby the information system, e.g. if an internet is involved, which maycomprise multiple, dynamically chosen paths. Information and/or a formatused for information may be packet-based, and/or be mapped, and/or bemappable and/or be intended for mapping, to packets. Alternatively, oradditionally, there may be considered a method for operating a targetdevice comprising providing a target indicating to an informationsystem. More alternatively, or additionally, a target device may beconsidered, the target device being adapted for providing a targetindication to an information system.

In another approach, there may be considered a target indication tooladapted for, and/or comprising an indication module for, providing atarget indication to an information system. The target device maygenerally be a target as described above. A target indication tool maycomprise, and/or be implemented as, software and/or application or app,and/or web interface or user interface, and/or may comprise one or moremodules for implementing actions performed and/or controlled by thetool. The tool and/or target device may be adapted for, and/or themethod may comprise, receiving a user input, based on which a targetindicating may be determined and/or provided. Alternatively, oradditionally, the tool and/or target device may be adapted for, and/orthe method may comprise, receiving information and/or communicationsignaling carrying information, and/or operating on, and/or presenting(e.g., on a screen and/or as audio or as other form of indication),information. The information may be based on received information and/orcommunication signaling carrying information. Presenting information maycomprise processing received information, e.g. decoding and/ortransforming, in particular between different formats, and/or forhardware used for presenting. Operating on information may beindependent of or without presenting, and/or proceed or succeedpresenting, and/or may be without user interaction or even userreception, for example for automatic processes, or target deviceswithout (e.g., regular) user interaction like MTC devices, of forautomotive or transport or industrial use. The information orcommunication signaling may be expected and/or received based on thetarget indication. Presenting and/or operating on information maygenerally comprise one or more processing steps, in particular decodingand/or executing and/or interpreting and/or transforming information.Operating on information may generally comprise relaying and/ortransmitting the information, e.g. on an air interface, which mayinclude mapping the information onto signaling (such mapping maygenerally pertain to one or more layers, e.g. one or more layers of anair interface, e.g. RLC (Radio Link Control) layer and/or MAC layerand/or physical layer/s). The information may be imprinted (or mapped)on communication signaling based on the target indication, which maymake it particularly suitable for use in a RAN (e.g., for a targetdevice like a network node or in particular a UE or terminal). The toolmay generally be adapted for use on a target device, like a UE orterminal. Generally, the tool may provide multiple functionalities, e.g.for providing and/or selecting the target indication, and/or presenting,e.g. video and/or audio, and/or operating on and/or storing receivedinformation. Providing a target indication may comprise transmitting ortransferring the indication as signaling, and/or carried on signaling,in a RAN, for example if the target device is a UE, or the tool for aUE. It should be noted that such provided information may be transferredto the information system via one or more additionally communicationinterfaces and/or paths and/or connections. The target indication may bea higher-layer indication and/or the information provided by theinformation system may be higher-layer information, e.g. applicationlayer or user-layer, in particular above radio layers like transportlayer and physical layer. The target indication may be mapped onphysical layer radio signaling, e.g. related to or on the user-plane,and/or the information may be mapped on physical layer radiocommunication signaling, e.g. related to or on the user-plane (inparticular, in reverse communication directions). The describedapproaches allow a target indication to be provided, facilitatinginformation to be provided in a specific format particularly suitableand/or adapted to efficiently use an air interface. A user input may forexample represent a selection from a plurality of possible transmissionmodes or formats, and/or paths, e.g. in terms of data rate and/orpackaging and/or size of information to be provided by the informationsystem.

In general, a numerology and/or subcarrier spacing may indicate thebandwidth (in frequency domain) of a subcarrier of a carrier, and/or thenumber of subcarriers in a carrier and/or the numbering of thesubcarriers in a carrier, and/or the symbol time length. Differentnumerologies may in particular be different in the bandwidth of asubcarrier. In some variants, all the subcarriers in a carrier have thesame bandwidth associated to them. The numerology and/or subcarrierspacing may be different between carriers in particular regarding thesubcarrier bandwidth. A symbol time length, and/or a time length of atiming structure pertaining to a carrier may be dependent on the carrierfrequency, and/or the subcarrier spacing and/or the numerology. Inparticular, different numerologies may have different symbol timelengths, even on the same carrier.

Signaling may generally comprise one or more (e.g., modulation) symbolsand/or signals and/or messages. A signal may comprise or represent oneor more bits. An indication may represent signaling, and/or beimplemented as a signal, or as a plurality of signals. One or moresignals may be included in and/or represented by a message. Signaling,in particular control signaling, may comprise a plurality of signalsand/or messages, which may be transmitted on different carriers and/orbe associated to different signaling processes, e.g. representing and/orpertaining to one or more such processes and/or correspondinginformation. An indication may comprise signaling, and/or a plurality ofsignals and/or messages and/or may be comprised therein, which may betransmitted on different carriers and/or be associated to differentacknowledgement signaling processes, e.g. representing and/or pertainingto one or more such processes. Signaling associated to a channel may betransmitted such that represents signaling and/or information for thatchannel, and/or that the signaling is interpreted by the transmitterand/or receiver to belong to that channel. Such signaling may generallycomply with transmission parameters and/or format/s for the channel.

An antenna arrangement may comprise one or more antenna elements(radiating elements), which may be combined in antenna arrays. Anantenna array or subarray may comprise one antenna element, or aplurality of antenna elements, which may be arranged e.g. twodimensionally (for example, a panel) or three dimensionally. It may beconsidered that each antenna array or subarray or element is separatelycontrollable, respectively that different antenna arrays arecontrollable separately from each other. A single antennaelement/radiator may be considered the smallest example of a subarray.Examples of antenna arrays comprise one or more multi-antenna panels orone or more individually controllable antenna elements. An antennaarrangement may comprise a plurality of antenna arrays. It may beconsidered that an antenna arrangement is associated to a (specificand/or single) radio node, e.g. a configuring or informing or schedulingradio node, e.g. to be controlled or controllable by the radio node. Anantenna arrangement associated to a UE or terminal may be smaller (e.g.,in size and/or number of antenna elements or arrays) than the antennaarrangement associated to a network node. Antenna elements of an antennaarrangement may be configurable for different arrays, e.g. to change thebeamforming characteristics. In particular, antenna arrays may be formedby combining one or more independently or separately controllableantenna elements or subarrays. The beams may be provided by analogbeamforming, or in some variants by digital beamforming, or by hybridbeamforming combing analog and digital beamforming. The informing radionodes may be configured with the manner of beam transmission, e.g. bytransmitting a corresponding indicator or indication, for example asbeam identify indication. However, there may be considered cases inwhich the informing radio node/s are not configured with suchinformation, and/or operate transparently, not knowing the way ofbeamforming used. An antenna arrangement may be considered separatelycontrollable in regard to the phase and/or amplitude/power and/or gainof a signal feed to it for transmission, and/or separately controllableantenna arrangements may comprise an independent or separate transmitand/or receive unit and/or ADC (Analog-Digital-Converter, alternativelyan ADC chain) or DCA (Digital-to-Analog Converter, alternatively a DCAchain) to convert digital control information into an analog antennafeed for the whole antenna arrangement (the ADC/DCA may be consideredpart of, and/or connected or connectable to, antenna circuitry) or viceversa. A scenario in which an ADC or DCA is controlled directly forbeamforming may be considered an analog beamforming scenario; suchcontrolling may be performed after encoding/decoding and/or aftermodulation symbols have been mapped to resource elements. This may be onthe level of antenna arrangements using the same ADC/DCA, e.g. oneantenna element or a group of antenna elements associated to the sameADC/DCA. Digital beamforming may correspond to a scenario in whichprocessing for beamforming is provided before feeding signaling to theADC/DCA, e.g. by using one or more precoder/s and/or by precodinginformation, for example before and/or when mapping modulation symbolsto resource elements. Such a precoder for beamforming may provideweights, e.g. for amplitude and/or phase, and/or may be based on a(precoder) codebook, e.g. selected from a codebook. A precoder maypertain to one beam or more beams, e.g. defining the beam or beams. Thecodebook may be configured or configurable, and/or be predefined. DFTbeamforming may be considered a form of digital beamforming, wherein aDFT procedure is used to form one or more beams. Hybrid forms ofbeamforming may be considered.

A beam may be defined by a spatial and/or angular and/or spatial angulardistribution of radiation and/or a spatial angle (also referred to assolid angle) or spatial (solid) angle distribution into which radiationis transmitted (for transmission beamforming) or from which it isreceived (for reception beamforming). Reception beamforming may compriseonly accepting signals coming in from a reception beam (e.g., usinganalog beamforming to not receive outside reception beam/s), and/orsorting out signals that do not come in in a reception beam, e.g. indigital postprocessing, e.g. digital beamforming. A beam may have asolid angle equal to or smaller than 4*pi sr (4*pi correspond to a beamcovering all directions), in particular smaller than 2*pi, or pi, orpi/2, or pi/4 or pi/8 or pi/16. In particular for high frequencies,smaller beams may be used. Different beams may have different directionsand/or sizes (e.g., solid angle and/or reach). A beam may have a maindirection, which may be defined by a main lobe (e.g., center of the mainlobe, e.g. pertaining to signal strength and/or solid angle, which maybe averaged and/or weighted to determine the direction), and may haveone or more sidelobes. A lobe may generally be defined to have acontinuous or contiguous distribution of energy and/or power transmittedand/or received, e.g. bounded by one or more contiguous or contiguousregions of zero energy (or practically zero energy). A main lobe maycomprise the lobe with the largest signal strength and/or energy and/orpower content. However, sidelobes usually appear due to limitations ofbeamforming, some of which may carry signals with significant strength,and may cause multi-path effects. A sidelobe may generally have adifferent direction than a main lobe and/or other side lobes, however,due to reflections a sidelobe still may contribute to transmitted and/orreceived energy or power. A beam may be swept and/or switched over time,e.g., such that its (main) direction is changed, but its shape(angular/solid angle distribution) around the main direction is notchanged, e.g. from the transmitter's views for a transmission beam, orthe receiver's view for a reception beam, respectively. Sweeping maycorrespond to continuous or near continuous change of main direction(e.g., such that after each change, the main lobe from before the changecovers at least partly the main lobe after the change, e.g. at least to50 or 75 or 90 percent). Switching may correspond to switching directionnon-continuously, e.g. such that after each change, the main lobe frombefore the change does not cover the main lobe after the change, e.g. atmost to 50 or 25 or 10 percent.

Signal strength may be a representation of signal power and/or signalenergy, e.g. as seen from a transmitting node or a receiving node. Abeam with larger strength at transmission (e.g., according to thebeamforming used) than another beam does may not necessarily have largerstrength at the receiver, and vice versa, for example due tointerference and/or obstruction and/or dispersion and/or absorptionand/or reflection and/or attrition or other effects influencing a beamor the signaling it carries. Signal quality may in general be arepresentation of how well a signal may be received over noise and/orinterference. A beam with better signal quality than another beam doesnot necessarily have a larger beam strength than the other beam. Signalquality may be represented for example by SIR, SNR, SINR, BER, BLER,Energy per resource element over noise/interference or anothercorresponding quality measure. Signal quality and/or signal strength maypertain to, and/or may be measured with respect to, a beam, and/orspecific signaling carried by the beam, e.g. reference signaling and/ora specific channel, e.g. a data channel or control channel. Signalstrength may be represented by received signal strength, and/or relativesignal strength, e.g. in comparison to a reference signal (strength).

Uplink or sidelink signaling may be OFDMA (Orthogonal Frequency DivisionMultiple Access) or SC-FDMA (Single Carrier Frequency Division MultipleAccess) signaling. Downlink signaling may in particular be OFDMAsignaling. However, signaling is not limited thereto (Filter-Bank basedsignaling and/or Single-Carrier based signaling, e.g. SC-FDE signaling,may be considered alternatives).

A radio node may generally be considered a device or node adapted forwireless and/or radio (and/or millimeter wave) frequency communication,and/or for communication utilising an air interface, e.g. according to acommunication standard.

A radio node may be a network node, or a user equipment or terminal. Anetwork node may be any radio node of a wireless communication network,e.g. a base station and/or gNodeB (gNB) and/or eNodeB (eNB) and/or relaynode and/or micro/nano/pico/femto node and/or transmission point (TP)and/or access point (AP) and/or other node, in particular for a RAN orother wireless communication network as described herein.

The terms user equipment (UE) and terminal may be considered to beinterchangeable in the context of this disclosure. A wireless device,user equipment or terminal may represent an end device for communicationutilising the wireless communication network, and/or be implemented as auser equipment according to a standard. Examples of user equipments maycomprise a phone like a smartphone, a personal communication device, amobile phone or terminal, a computer, in particular laptop, a sensor ormachine with radio capability (and/or adapted for the air interface), inparticular for MTC (Machine-Type-Communication, sometimes also referredto M2M, Machine-To-Machine), or a vehicle adapted for wirelesscommunication. A user equipment or terminal may be mobile or stationary.A wireless device generally may comprise, and/or be implemented as,processing circuitry and/or radio circuitry, which may comprise one ormore chips or sets of chips. The circuitry and/or circuitries may bepackaged, e.g. in a chip housing, and/or may have one or more physicalinterfaces to interact with other circuitry and/or for power supply.Such a wireless device may be intended for use in a user equipment orterminal.

A radio node may generally comprise processing circuitry and/or radiocircuitry. A radio node, in particular a network node, may in some casescomprise cable circuitry and/or communication circuitry, with which itmay be connected or connectable to another radio node and/or a corenetwork.

Circuitry may comprise integrated circuitry. Processing circuitry maycomprise one or more processors and/or controllers (e.g.,microcontrollers), and/or ASICs (Application Specific IntegratedCircuitry) and/or FPGAs (Field Programmable Gate Array), or similar. Itmay be considered that processing circuitry comprises, and/or is(operatively) connected or connectable to one or more memories or memoryarrangements. A memory arrangement may comprise one or more memories. Amemory may be adapted to store digital information. Examples formemories comprise volatile and non-volatile memory, and/or Random AccessMemory (RAM), and/or Read-Only-Memory (ROM), and/or magnetic and/oroptical memory, and/or flash memory, and/or hard disk memory, and/orEPROM or EEPROM (Erasable Programmable ROM or Electrically ErasableProgrammable ROM).

Radio circuitry may comprise one or more transmitters and/or receiversand/or transceivers (a transceiver may operate or be operable astransmitter and receiver, and/or may comprise joint or separatedcircuitry for receiving and transmitting, e.g. in one package orhousing), and/or may comprise one or more amplifiers and/or oscillatorsand/or filters, and/or may comprise, and/or be connected or connectableto antenna circuitry and/or one or more antennas and/or antenna arrays.An antenna array may comprise one or more antennas, which may bearranged in a dimensional array, e.g. 2D or 3D array, and/or antennapanels. A remote radio head (RRH) may be considered as an example of anantenna array. However, in some variants, an RRH may be also beimplemented as a network node, depending on the kind of circuitry and/orfunctionality implemented therein.

Communication circuitry may comprise radio circuitry and/or cablecircuitry. Communication circuitry generally may comprise one or moreinterfaces, which may be air interface/s and/or cable interface/s and/oroptical interface/s, e.g. laser-based. Interface/s may be in particularpacket-based. Cable circuitry and/or a cable interfaces may comprise,and/or be connected or connectable to, one or more cables (e.g., opticalfiber-based and/or wire-based), which may be directly or indirectly(e.g., via one or more intermediate systems and/or interfaces) beconnected or connectable to a target, e.g. controlled by communicationcircuitry and/or processing circuitry.

Any one or all of the modules disclosed herein may be implemented insoftware and/or firmware and/or hardware. Different modules may beassociated to different components of a radio node, e.g. differentcircuitries or different parts of a circuitry. It may be considered thata module is distributed over different components and/or circuitries. Aprogram product as described herein may comprise the modules related toa device on which the program product is intended (e.g., a userequipment or network node) to be executed (the execution may beperformed on, and/or controlled by the associated circuitry).

A wireless communication network may be or comprise a radio accessnetwork and/or a backhaul network (e.g. a relay or backhaul network oran IAB network), and/or a Radio Access Network (RAN) in particularaccording to a communication standard. A communication standard may inparticular a standard according to 3GPP and/or 5G, e.g. according to NRor LTE, in particular LTE Evolution.

A wireless communication network may be and/or comprise a Radio AccessNetwork (RAN), which may be and/or comprise any kind of cellular and/orwireless radio network, which may be connected or connectable to a corenetwork. The approaches described herein are particularly suitable for a5G network, e.g. LTE Evolution and/or NR (New Radio), respectivelysuccessors thereof. A RAN may comprise one or more network nodes, and/orone or more terminals, and/or one or more radio nodes. A network nodemay in particular be a radio node adapted for radio and/or wirelessand/or cellular communication with one or more terminals. A terminal maybe any device adapted for radio and/or wireless and/or cellularcommunication with or within a RAN, e.g. a user equipment (UE) or mobilephone or smartphone or computing device or vehicular communicationdevice or device for machine-type-communication (MTC), etc. A terminalmay be mobile, or in some cases stationary. A RAN or a wirelesscommunication network may comprise at least one network node and a UE,or at least two radio nodes. There may be generally considered awireless communication network or system, e.g. a RAN or RAN system,comprising at least one radio node, and/or at least one network node andat least one terminal.

Transmitting in downlink may pertain to transmission from the network ornetwork node to the terminal. Transmitting in uplink may pertain totransmission from the terminal to the network or network node.Transmitting in sidelink may pertain to (direct) transmission from oneterminal to another. Uplink, downlink and sidelink (e.g., sidelinktransmission and reception) may be considered communication directions.In some variants, uplink and downlink may also be used to describedwireless communication between network nodes, e.g. for wireless backhauland/or relay communication and/or (wireless) network communication forexample between base stations or similar network nodes, in particularcommunication terminating at such. It may be considered that backhauland/or relay communication and/or network communication is implementedas a form of sidelink or uplink communication or similar thereto.

Control information or a control information message or correspondingsignaling (control signaling) may be transmitted on a control channel,e.g. a physical control channel, which may be a downlink channel or (ora sidelink channel in some cases, e.g. one UE scheduling another UE).For example, control information/allocation information may be signaledby a network node on PDCCH (Physical Downlink Control Channel) and/or aPDSCH (Physical Downlink Shared Channel) and/or a HARQ-specific channel.Acknowledgement signaling, e.g. as a form of control information orsignaling like uplink control information/signaling, may be transmittedby a terminal on a PUCCH (Physical Uplink Control Channel) and/or PUSCH(Physical Uplink Shared Channel) and/or a HARQ-specific channel.Multiple channels may apply for multi-component/multi-carrier indicationor signaling.

Transmitting acknowledgement signaling may in general be based on and/orin response to subject transmission, and/or to control signalingscheduling subject transmission. Such control signaling and/or subjectsignaling may be transmitted by a signaling radio node (which may be anetwork node, and/or a node associated to it, e.g. in a dualconnectivity scenario. Subject transmission and/or subject signaling maybe transmission or signaling to which ACK/NACK or acknowledgementinformation pertains, e.g. indicating correct or incorrect receptionand/or decoding of the subject transmission or signaling. Subjectsignaling or transmission may in particular comprise and/or berepresented by data signaling, e.g. on a PDSCH or PSSCH, or some formsof control signaling, e.g. on a PDCCH or PSSCH, for example for specificformats.

A signaling characteristic may be based on a type or format of ascheduling grant and/or scheduling assignment, and/or type ofallocation, and/or timing of acknowledgement signaling and/or thescheduling grant and/or scheduling assignment, and/or resourcesassociated to acknowledgement signaling and/or the scheduling grantand/or scheduling assignment. For example, if a specific format for ascheduling grant (scheduling or allocating the allocated resources) orscheduling assignment (scheduling the subject transmission foracknowledgement signaling) is used or detected, the first or secondcommunication resource may be used. Type of allocation may pertain todynamic allocation (e.g., using DCI/PDCCH) or semi-static allocation(e.g., for a configured grant). Timing of acknowledgement signaling maypertain to a slot and/or symbol/s the signaling is to be transmitted.Resources used for acknowledgement signaling may pertain to theallocated resources. Timing and/or resources associated to a schedulinggrant or assignment may represent a search space or CORESET (a set ofresources configured for reception of PDCCH transmissions) in which thegrant or assignment is received. Thus, which transmission resource to beused may be based on implicit conditions, requiring low signalingoverhead.

Scheduling may comprise indicating, e.g. with control signaling like DCIor SCI signaling and/or signaling on a control channel like PDCCH orPSCCH, one or more scheduling opportunities of a configuration intendedto carry data signaling or subject signaling. The configuration may berepresented or representable by, and/or correspond to, a table. Ascheduling assignment may for example point to an opportunity of thereception allocation configuration, e.g. indexing a table of schedulingopportunities. In some cases, a reception allocation configuration maycomprise 15 or 16 scheduling opportunities. The configuration may inparticular represent allocation in time. It may be considered that thereception allocation configuration pertains to data signaling, inparticular on a physical data channel like PDSCH or PSSCH. In general,the reception allocation configuration may pertain to downlinksignaling, or in some scenarios to sidelink signaling. Control signalingscheduling subject transmission like data signaling may point and/orindex and/or refer to and/or indicate a scheduling opportunity of thereception allocation configuration. It may be considered that thereception allocation configuration is configured or configurable withhigher-layer signaling, e.g. RRC or MAC layer signaling. The receptionallocation configuration may be applied and/or applicable and/or validfor a plurality of transmission timing intervals, e.g. such that foreach interval, one or more opportunities may be indicated or allocatedfor data signaling. These approaches allow efficient and flexiblescheduling, which may be semi-static, but may updated or reconfigured onuseful timescales in response to changes of operation conditions.

Control information, e.g., in a control information message, in thiscontext may in particular be implemented as and/or represented by ascheduling assignment, which may indicate subject transmission forfeedback (transmission of acknowledgement signaling), and/or reportingtiming and/or frequency resources and/or code resources. Reportingtiming may indicate a timing for scheduled acknowledgement signaling,e.g. slot and/or symbol and/or resource set. Control information may becarried by control signaling.

Subject transmissions may comprise one or more individual transmissions.Scheduling assignments may comprise one or more scheduling assignments.It should generally be noted that in a distributed system, subjecttransmissions, configuration and/or scheduling may be provided bydifferent nodes or devices or transmission points. Different subjecttransmissions may be on the same carrier or different carriers (e.g., ina carrier aggregation), and/or same or different bandwidth parts, and/oron the same or different layers or beams, e.g. in a MIMO scenario,and/or to same or different ports. Generally, subject transmissions maypertain to different HARQ or ARQ processes (or different sub-processes,e.g. in MIMO with different beams/layers associated to the same processidentifier, but different sub-process-identifiers like swap bits). Ascheduling assignment and/or a HARQ codebook may indicate a target HARQstructure. A target HARQ structure may for example indicate an intendedHARQ response to a subject transmission, e.g. the number of bits and/orwhether to provide code block group level response or not. However, itshould be noted that the actual structure used may differ from thetarget structure, e.g. due to the total size of target structures for asubpattern being larger than the predetermined size.

Transmitting acknowledgement signaling, also referred to as transmittingacknowledgement information or feedback information or simply as ARQ orHARQ feedback or feedback or reporting feedback, may comprise, and/or bebased on determining correct or incorrect reception of subjecttransmission/s, e.g. based on error coding and/or based on schedulingassignment/s scheduling the subject transmissions. Transmittingacknowledgement information may be based on, and/or comprise, astructure for acknowledgement information to transmit, e.g. thestructure of one or more subpatterns, e.g. based on which subjecttransmission is scheduled for an associated subdivision. Transmittingacknowledgement information may comprise transmitting correspondingsignaling, e.g. at one instance and/or in one message and/or onechannel, in particular a physical channel, which may be a controlchannel. In some cases, the channel may be a shared channel or datachannel, e.g. utilising rate-matching of the acknowledgment information.The acknowledgement information may generally pertain to a plurality ofsubject transmissions, which may be on different channels and/orcarriers, and/or may comprise data signaling and/or control signaling.The acknowledgment information may be based on a codebook, which may bebased on one or more size indications and/or assignment indications(representing HARQ structures), which may be received with a pluralityof control signalings and/or control messages, e.g. in the same ordifferent transmission timing structures, and/or in the same ordifferent (target) sets of resources. Transmitting acknowledgementinformation may comprise determining the codebook, e.g. based on controlinformation in one or more control information messages and/or aconfiguration. A codebook may pertain to transmitting acknowledgementinformation at a single and/or specific instant, e.g. a single PUCCH orPUSCH transmission, and/or in one message or with jointly encoded and/ormodulated acknowledgement information. Generally, acknowledgmentinformation may be transmitted together with other control information,e.g. a scheduling request and/or measurement information.

Acknowledgement signaling may in some cases comprise, next toacknowledgement information, other information, e.g. controlinformation, in particular, uplink or sidelink control information, likea scheduling request and/or measurement information, or similar, and/orerror detection and/or correction information, respectively associatedbits. The payload size of acknowledgement signaling may represent thenumber of bits of acknowledgement information, and/or in some cases thetotal number of bits carried by the acknowledgement signaling, and/orthe number of resource elements needed. Acknowledgement signaling and/orinformation may pertain to ARQ and/or HARQ processes; an ARQ process mayprovide ACK/NACK (and perhaps additional feedback) feedback, anddecoding may be performed on each (re-)transmission separately, withoutsoft-buffering/soft-combining intermediate data, whereas HARQ maycomprise soft-buffering/soft-combining of intermediate data of decodingfor one or more (re-)transmissions.

Subject transmission may be data signaling or control signaling. Thetransmission may be on a shared or dedicated channel. Data signaling maybe on a data channel, for example on a PDSCH or PSSCH, or on a dedicateddata channel, e.g. for low latency and/or high reliability, e.g. a URLLCchannel. Control signaling may be on a control channel, for example on acommon control channel or a PDCCH or PSCCH, and/or comprise one or moreDCI messages or SCI messages. In some cases, the subject transmissionmay comprise, or represent, reference signaling. For example, it maycomprise DM-RS and/or pilot signaling and/or discovery signaling and/orsounding signaling and/or phase tracking signaling and/or cell-specificreference signaling and/or user-specific signaling, in particularCSI-RS. A subject transmission may pertain to one scheduling assignmentand/or one acknowledgement signaling process (e.g., according toidentifier or subidentifier), and/or one subdivision. In some cases, asubject transmission may cross the borders of subdivisions in time, e.g.due to being scheduled to start in one subdivision and extending intoanother, or even crossing over more than one subdivision. In this case,it may be considered that the subject transmission is associated to thesubdivision it ends in.

It may be considered that transmitting acknowledgement information, inparticular of acknowledgement information, is based on determiningwhether the subject transmission/s has or have been received correctly,e.g. based on error coding and/or reception quality. Reception qualitymay for example be based on a determined signal quality. Acknowledgementinformation may generally be transmitted to a signaling radio nodeand/or node arrangement and/or to a network and/or network node.

Acknowledgement information, or bit/s of a subpattern structure of suchinformation (e.g., an acknowledgement information structure, mayrepresent and/or comprise one or more bits, in particular a pattern ofbits. Multiple bits pertaining to a data structure or substructure ormessage like a control message may be considered a subpattern. Thestructure or arrangement of acknowledgement information may indicate theorder, and/or meaning, and/or mapping, and/or pattern of bits (orsubpatterns of bits) of the information. The structure or mapping may inparticular indicate one or more data block structures, e.g. code blocksand/or code block groups and/or transport blocks and/or messages, e.g.command messages, the acknowledgement information pertains to, and/orwhich bits or subpattern of bits are associated to which data blockstructure. In some cases, the mapping may pertain to one or moreacknowledgement signaling processes, e.g. processes with differentidentifiers, and/or one or more different data streams. Theconfiguration or structure or codebook may indicate to which process/esand/or data stream/s the information pertains. Generally, theacknowledgement information may comprise one or more subpatterns, eachof which may pertain to a data block structure, e.g. a code block orcode block group or transport block. A subpattern may be arranged toindicate acknowledgement or non-acknowledgement, or anotherretransmission state like non-scheduling or non-reception, of theassociated data block structure. It may be considered that a subpatterncomprises one bit, or in some cases more than one bit. It should benoted that acknowledgement information may be subjected to significantprocessing before being transmitted with acknowledgement signaling.Different configurations may indicate different sizes and/or mappingand/or structures and/or pattern.

An acknowledgment signaling process (providing acknowledgmentinformation) may be a HARQ process, and/or be identified by a processidentifier, e.g. a HARQ process identifier or subidentifier.Acknowledgement signaling and/or associated acknowledgement informationmay be referred to as feedback or acknowledgement feedback. It should benoted that data blocks or structures to which subpatterns may pertainmay be intended to carry data (e.g., information and/or systemic and/orcoding bits). However, depending on transmission conditions, such datamay be received or not received (or not received correctly), which maybe indicated correspondingly in the feedback. In some cases, asubpattern of acknowledgement signaling may comprise padding bits, e.g.if the acknowledgement information for a data block requires fewer bitsthan indicated as size of the subpattern. Such may for example happen ifthe size is indicated by a unit size larger than required for thefeedback.

Acknowledgment information may generally indicate at least ACK or NACK,e.g. pertaining to an acknowledgment signaling process, or an element ofa data block structure like a data block, subblock group or subblock, ora message, in particular a control message. Generally, to anacknowledgment signaling process there may be associated one specificsubpattern and/or a data block structure, for which acknowledgmentinformation may be provided. Acknowledgement information may comprise aplurality of pieces of information, represented in a plurality of ARQand/or HARQ structures.

An acknowledgment signaling process may determine correct or incorrectreception, and/or corresponding acknowledgement information, of a datablock like a transport block, and/or substructures thereof, based oncoding bits associated to the data block, and/or based on coding bitsassociated to one or more data block and/or subblocks and/or subblockgroup/s. Acknowledgement information (determined by an acknowledgementsignaling process) may pertain to the data block as a whole, and/or toone or more subblocks or subblock groups. A code block may be consideredan example of a subblock, whereas a code block group may be consideredan example of a subblock group. Accordingly, the associated subpatternmay comprise one or more bits indicating reception status or feedback ofthe data block, and/or one or more bits indicating reception status orfeedback of one or more subblocks or subblock groups. Each subpattern orbit of the subpattern may be associated and/or mapped to a specific datablock or subblock or subblock group. In some variants, correct receptionfor a data block may be indicated if all subblocks or subblock groupsare correctly identified. In such a case, the subpattern may representacknowledgement information for the data block as a whole, reducingoverhead in comparison to provide acknowledgement information for thesubblocks or subblock groups. The smallest structure (e.g.subblock/subblock group/data block) the subpattern providesacknowledgement information for and/or is associated to may beconsidered its (highest) resolution. In some variants, a subpattern mayprovide acknowledgment information regarding several elements of a datablock structure and/or at different resolution, e.g. to allow morespecific error detection. For example, even if a subpattern indicatesacknowledgment signaling pertaining to a data block as a whole, in somevariants higher resolution (e.g., subblock or subblock group resolution)may be provided by the subpattern. A subpattern may generally compriseone or more bits indicating ACK/NACK for a data block, and/or one ormore bits for indicating ACK/NACK for a subblock or subblock group, orfor more than one subblock or subblock group.

A subblock and/or subblock group may comprise information bits(representing the data to be transmitted, e.g. user data and/ordownlink/sidelink data or uplink data). It may be considered that a datablock and/or subblock and/or subblock group also comprises error one ormore error detection bits, which may pertain to, and/or be determinedbased on, the information bits (for a subblock group, the errordetection bit/s may be determined based on the information bits and/orerror detection bits and/or error correction bits of the subblock/s ofthe subblock group). A data block or substructure like subblock orsubblock group may comprise error correction bits, which may inparticular be determined based on the information bits and errordetection bits of the block or substructure, e.g. utilising an errorcorrection coding scheme, in particular for forward error correction(FEC), e.g. LDPC or polar coding and/or turbo coding. Generally, theerror correction coding of a data block structure (and/or associatedbits) may cover and/or pertain to information bits and error detectionbits of the structure. A subblock group may represent a combination ofone or more code blocks, respectively the corresponding bits. A datablock may represent a code block or code block group, or a combinationof more than one code block groups. A transport block may be split up incode blocks and/or code block groups, for example based on the bit sizeof the information bits of a higher layer data structure provided forerror coding and/or size requirements or preferences for error coding,in particular error correction coding. Such a higher layer datastructure is sometimes also referred to as transport block, which inthis context represents information bits without the error coding bitsdescribed herein, although higher layer error handling information maybe included, e.g. for an internet protocol like TCP. However, such errorhandling information represents information bits in the context of thisdisclosure, as the acknowledgement signaling procedures described treatit accordingly.

In some variants, a subblock like a code block may comprise errorcorrection bits, which may be determined based on the information bit/sand/or error detection bit/s of the subblock. An error correction codingscheme may be used for determining the error correction bits, e.g. basedon LDPC or polar coding or Reed-Mueller coding. In some cases, asubblock or code block may be considered to be defined as a block orpattern of bits comprising information bits, error detection bit/sdetermined based on the information bits, and error correction bit/sdetermined based on the information bits and/or error detection bit/s.It may be considered that in a subblock, e.g. code block, theinformation bits (and possibly the error correction bit/s) are protectedand/or covered by the error correction scheme or corresponding errorcorrection bit/s. A code block group may comprise one or more codeblocks. In some variants, no additional error detection bits and/orerror correction bits are applied, however, it may be considered toapply either or both. A transport block may comprise one or more codeblock groups. It may be considered that no additional error detectionbits and/or error correction bits are applied to a transport block,however, it may be considered to apply either or both. In some specificvariants, the code block group/s comprise no additional layers of errordetection or correction coding, and the transport block may compriseonly additional error detection coding bits, but no additional errorcorrection coding. This may particularly be true if the transport blocksize is larger than the code block size and/or the maximum size forerror correction coding. A subpattern of acknowledgement signaling (inparticular indicating ACK or NACK) may pertain to a code block, e.g.indicating whether the code block has been correctly received. It may beconsidered that a subpattern pertains to a subgroup like a code blockgroup or a data block like a transport block. In such cases, it mayindicate ACK, if all subblocks or code blocks of the group ordata/transport block are received correctly (e.g. based on a logical ANDoperation), and NACK or another state of non-correct reception if atleast one subblock or code block has not been correctly received. Itshould be noted that a code block may be considered to be correctlyreceived not only if it actually has been correctly received, but alsoif it can be correctly reconstructed based on soft-combining and/or theerror correction coding.

A subpattern/HARQ structure may pertain to one acknowledgement signalingprocess and/or one carrier like a component carrier and/or data blockstructure or data block. It may in particular be considered that one(e.g. specific and/or single) subpattern pertains, e.g. is mapped by thecodebook, to one (e.g., specific and/or single) acknowledgementsignaling process, e.g. a specific and/or single HARQ process. It may beconsidered that in the bit pattern, subpatterns are mapped toacknowledgement signaling processes and/or data blocks or data blockstructures on a one-to-one basis. In some variants, there may bemultiple subpatterns (and/or associated acknowledgment signalingprocesses) associated to the same component carrier, e.g. if multipledata streams transmitted on the carrier are subject to acknowledgementsignaling processes. A subpattern may comprise one or more bits, thenumber of which may be considered to represent its size or bit size.Different bit n-tupels (n being 1 or larger) of a subpattern may beassociated to different elements of a data block structure (e.g., datablock or subblock or subblock group), and/or represent differentresolutions. There may be considered variants in which only oneresolution is represented by a bit pattern, e.g. a data block. A bitn-tupel may represent acknowledgement information (also referred to afeedback), in particular ACK or NACK, and optionally, (if n>1), mayrepresent DTX/DRX or other reception states. ACK/NACK may be representedby one bit, or by more than one bit, e.g. to improve disambiguity of bitsequences representing ACK or NACK, and/or to improve transmissionreliability.

The acknowledgement information or feedback information may pertain to aplurality of different transmissions, which may be associated to and/orrepresented by data block structures, respectively the associated datablocks or data signaling. The data block structures, and/or thecorresponding blocks and/or signaling, may be scheduled for simultaneoustransmission, e.g. for the same transmission timing structure, inparticular within the same slot or subframe, and/or on the samesymbol/s. However, alternatives with scheduling for non-simultaneoustransmission may be considered. For example, the acknowledgmentinformation may pertain to data blocks scheduled for differenttransmission timing structures, e.g. different slots (or mini-slots, orslots and mini-slots) or similar, which may correspondingly be received(or not or wrongly received). Scheduling signaling may generallycomprise indicating resources, e.g. time and/or frequency resources, forexample for receiving or transmitting the scheduled signaling.

Signaling may generally be considered to represent an electromagneticwave structure (e.g., over a time interval and frequency interval),which is intended to convey information to at least one specific orgeneric (e.g., anyone who might pick up the signaling) target. A processof signaling may comprise transmitting the signaling. Transmittingsignaling, in particular control signaling or communication signaling,e.g. comprising or representing acknowledgement signaling and/orresource requesting information, may comprise encoding and/ormodulating. Encoding and/or modulating may comprise error detectioncoding and/or forward error correction encoding and/or scrambling.Receiving control signaling may comprise corresponding decoding and/ordemodulation. Error detection coding may comprise, and/or be based on,parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check).Forward error correction coding may comprise and/or be based on forexample turbo coding and/or Reed-Muller coding, and/or polar codingand/or LDPC coding (Low Density Parity Check). The type of coding usedmay be based on the channel (e.g., physical channel) the coded signal isassociated to. A code rate may represent the ratio of the number ofinformation bits before encoding to the number of encoded bits afterencoding, considering that encoding adds coding bits for error detectioncoding and forward error correction. Coded bits may refer to informationbits (also called systematic bits) plus coding bits.

Communication signaling may comprise, and/or represent, and/or beimplemented as, data signaling, and/or user plane signaling.Communication signaling may be associated to a data channel, e.g. aphysical downlink channel or physical uplink channel or physicalsidelink channel, in particular a PDSCH (Physical Downlink SharedChannel) or PSSCH (Physical Sidelink Shared Channel). Generally, a datachannel may be a shared channel or a dedicated channel. Data signalingmay be signaling associated to and/or on a data channel.

An indication generally may explicitly and/or implicitly indicate theinformation it represents and/or indicates. Implicit indication may forexample be based on position and/or resource used for transmission.Explicit indication may for example be based on a parametrisation withone or more parameters, and/or one or more index or indices, and/or oneor more bit patterns representing the information. It may in particularbe considered that control signaling as described herein, based on theutilised resource sequence, implicitly indicates the control signalingtype.

A resource element may generally describe the smallest individuallyusable and/or encodable and/or decodable and/or modulatable and/ordemodulatable time-frequency resource, and/or may describe atime-frequency resource covering a symbol time length in time and asubcarrier in frequency. A signal may be allocatable and/or allocated toa resource element. A subcarrier may be a subband of a carrier, e.g. asdefined by a standard. A carrier may define a frequency and/or frequencyband for transmission and/or reception. In some variants, a signal(jointly encoded/modulated) may cover more than one resource elements. Aresource element may generally be as defined by a correspondingstandard, e.g. NR or LTE. As symbol time length and/or subcarrierspacing (and/or numerology) may be different between different symbolsand/or subcarriers, different resource elements may have differentextension (length/width) in time and/or frequency domain, in particularresource elements pertaining to different carriers.

A resource generally may represent a time-frequency and/or coderesource, on which signaling, e.g. according to a specific format, maybe communicated, for example transmitted and/or received, and/or beintended for transmission and/or reception.

A border symbol (or allocation unit) may generally represent a startingsymbol (allocation unit) or an ending symbol (allocation unit) fortransmitting and/or receiving. A starting symbol (or allocation unit)may in particular be a starting symbol of uplink or sidelink signaling,for example control signaling or data signaling. Such signaling may beon a data channel or control channel, e.g. a physical channel, inparticular a physical uplink shared channel (like PUSCH) or a sidelinkdata or shared channel, or a physical uplink control channel (likePUCCH) or a sidelink control channel. If the starting symbol (orallocation unit) is associated to control signaling (e.g., on a controlchannel), the control signaling may be in response to received signaling(in sidelink or downlink), e.g. representing acknowledgement signalingassociated thereto, which may be HARQ or ARQ signaling. An ending symbol(or allocation unit) may represent an ending symbol (in time) ofdownlink or sidelink transmission or signaling, which may be intended orscheduled for the radio node or user equipment. Such downlink signalingmay in particular be data signaling, e.g. on a physical downlink channellike a shared channel, e.g. a PDSCH (Physical Downlink Shared Channel).A starting symbol (or allocation unit) may be determined based on,and/or in relation to, such an ending symbol (or allocation unit).

Configuring a radio node, in particular a terminal or user equipment,may refer to the radio node being adapted or caused or set and/orinstructed to operate according to the configuration. Configuring may bedone by another device, e.g., a network node (for example, a radio nodeof the network like a base station or eNodeB) or network, in which caseit may comprise transmitting configuration data to the radio node to beconfigured. Such configuration data may represent the configuration tobe configured and/or comprise one or more instruction pertaining to aconfiguration, e.g. a configuration for transmitting and/or receiving onallocated resources, in particular frequency resources. A radio node mayconfigure itself, e.g., based on configuration data received from anetwork or network node. A network node may utilise, and/or be adaptedto utilise, its circuitry/ies for configuring. Allocation informationmay be considered a form of configuration data. Configuration data maycomprise and/or be represented by configuration information, and/or oneor more corresponding indications and/or message/s

Generally, configuring may include determining configuration datarepresenting the configuration and providing, e.g. transmitting, it toone or more other nodes (parallel and/or sequentially), which maytransmit it further to the radio node (or another node, which may berepeated until it reaches the wireless device). Alternatively, oradditionally, configuring a radio node, e.g., by a network node or otherdevice, may include receiving configuration data and/or data pertainingto configuration data, e.g., from another node like a network node,which may be a higher-level node of the network, and/or transmittingreceived configuration data to the radio node. Accordingly, determininga configuration and transmitting the configuration data to the radionode may be performed by different network nodes or entities, which maybe able to communicate via a suitable interface, e.g., an X2 interfacein the case of LTE or a corresponding interface for NR. Configuring aterminal may comprise scheduling downlink and/or uplink transmissionsfor the terminal, e.g. downlink data and/or downlink control signalingand/or DCI and/or uplink control or data or communication signaling, inparticular acknowledgement signaling, and/or configuring resourcesand/or a resource pool therefor.

A resource structure may be considered to be neighbored in frequencydomain by another resource structure, if they share a common borderfrequency, e.g. one as an upper frequency border and the other as alower frequency border. Such a border may for example be represented bythe upper end of a bandwidth assigned to a subcarrier n, which alsorepresents the lower end of a bandwidth assigned to a subcarrier n+1. Aresource structure may be considered to be neighbored in time domain byanother resource structure, if they share a common border time, e.g. oneas an upper (or right in the figures) border and the other as a lower(or left in the figures) border. Such a border may for example berepresented by the end of the symbol time interval assigned to a symboln, which also represents the beginning of a symbol time intervalassigned to a symbol n+1.

Generally, a resource structure being neighbored by another resourcestructure in a domain may also be referred to as abutting and/orbordering the other resource structure in the domain.

A resource structure may in general represent a structure in time and/orfrequency domain, in particular representing a time interval and afrequency interval. A resource structure may comprise and/or becomprised of resource elements, and/or the time interval of a resourcestructure may comprise and/or be comprised of symbol time interval/s,and/or the frequency interval of a resource structure may compriseand/or be comprised of subcarrier/s. A resource element may beconsidered an example for a resource structure, a slot or mini-slot or aPhysical Resource Block (PRB) or parts thereof may be considered others.A resource structure may be associated to a specific channel, e.g. aPUSCH or PUCCH, in particular resource structure smaller than a slot orPRB.

Examples of a resource structure in frequency domain comprise abandwidth or band, or a bandwidth part. A bandwidth part may be a partof a bandwidth available for a radio node for communicating, e.g. due tocircuitry and/or configuration and/or regulations and/or a standard. Abandwidth part may be configured or configurable to a radio node. Insome variants, a bandwidth part may be the part of a bandwidth used forcommunicating, e.g. transmitting and/or receiving, by a radio node. Thebandwidth part may be smaller than the bandwidth (which may be a devicebandwidth defined by the circuitry/configuration of a device, and/or asystem bandwidth, e.g. available for a RAN). It may be considered that abandwidth part comprises one or more resource blocks or resource blockgroups, in particular one or more PRBs or PRB groups. A bandwidth partmay pertain to, and/or comprise, one or more carriers. A resourcestructure may in time domain comprise and/or represent a time interval,e.g. one of more allocation units and/or symbols and/or slots and/orsubframes. In general, any reference to a symbol as a time interval maybe considered as a reference to an allocation unit as a more generalterm, unless the reference to the symbol is specific, e.g. referring toa specific division or modulation technique, or to modulation symbols astransmission structures.

A carrier may generally represent a frequency range or band and/orpertain to a central frequency and an associated frequency interval. Itmay be considered that a carrier comprises a plurality of subcarriers. Acarrier may have assigned to it a central frequency or center frequencyinterval, e.g. represented by one or more subcarriers (to eachsubcarrier there may be generally assigned a frequency bandwidth orinterval). Different carriers may be non-overlapping, and/or may beneighboring in frequency domain.

It should be noted that the term “radio” in this disclosure may beconsidered to pertain to wireless communication in general, and may alsoinclude wireless communication utilising millimeter waves, in particularabove one of the thresholds 10 GHz or 20 GHz or 50 GHz or 52 GHz or 52.6GHz or 60 GHz or 72 GHz or 100 GHz or 114 GHz. Such communication mayutilise one or more carriers, e.g. in FDD and/or carrier aggregation.Upper frequency boundaries may correspond to 300 GHz or 200 GHz or 120GHz or any of the thresholds larger than the one representing the lowerfrequency boundary.

A radio node, in particular a network node or a terminal, may generallybe any device adapted for transmitting and/or receiving radio and/orwireless signals and/or data, in particular communication data, inparticular on at least one carrier. The at least one carrier maycomprise a carrier accessed based on an LBT procedure (which may becalled LBT carrier), e.g., an unlicensed carrier. It may be consideredthat the carrier is part of a carrier aggregate.

Receiving or transmitting on a cell or carrier may refer to receiving ortransmitting utilizing a frequency (band) or spectrum associated to thecell or carrier. A cell may generally comprise and/or be defined by orfor one or more carriers, in particular at least one carrier for ULcommunication/transmission (called UL carrier) and at least one carrierfor DL communication/transmission (called DL carrier). It may beconsidered that a cell comprises different numbers of UL carriers and DLcarriers. Alternatively, or additionally, a cell may comprise at leastone carrier for UL communication/transmission and DLcommunication/transmission, e.g., in TDD-based approaches.

A channel may generally be a logical, transport or physical channel. Achannel may comprise and/or be arranged on one or more carriers, inparticular a plurality of subcarriers. A channel carrying and/or forcarrying control signaling/control information may be considered acontrol channel, in particular if it is a physical layer channel and/orif it carries control plane information. Analogously, a channel carryingand/or for carrying data signaling/user information may be considered adata channel, in particular if it is a physical layer channel and/or ifit carries user plane information. A channel may be defined for aspecific communication direction, or for two complementary communicationdirections (e.g., UL and DL, or sidelink in two directions), in whichcase it may be considered to have two component channels, one for eachdirection. Examples of channels comprise a channel for low latencyand/or high reliability transmission, in particular a channel forUltra-Reliable Low Latency Communication (URLLC), which may be forcontrol and/or data.

A control region generally may comprise time and/or frequency domainresources. A control region may be intended and/or indicated and/orconfigured, e.g. with higher layer signaling, for transmission ofcontrol signaling, in particular first control signaling. A controlregion may be periodic or aperiodic; in some cases, it may repeat atcertain time intervals (e.g., within a larger time interval) or be setor triggered or indicated for limited usage, e.g. in general in relationto a timing structure like a frame structure associated to the wirelesscommunication network and/or used therein. A control region may berepresented by a CORESET or a resource set in time and/or frequencydomain. To a control region, there may be associated a search space. Thesearch space may contain and/or be based on the control region. In thisdisclosure, features associated to a control region may be associated tothe associated search space and vice versa. A search space may provideparameters and/or features associated to control signaling to beexpected and/or processed and/or received and/or transmitted on resourceof the control region, e.g. one or more signaling characteristics ofcontrol signaling associated to the search space, e.g. type of controlsignaling (e.g., format) and/or allowable aggregation level and/orpossible location in the control region. It should be noted that thecontrol region may be shifted in time domain from the perspective of thetransmitter and receiver, e.g. due to delay effects and/or travel timeof signaling. However, the same term will be used for both perspectives,as there will be an unambiguous association; in particular, thetransmitter will intend reception in the control region of the receiver.A control region and/or search space may be configured by a network,e.g. a transmitting radio node, e.g. with higher layer signaling and/orbroadcast signaling. A search space may be device-specific (e.g.,configured specifically for one device, and/or with unicast signaling)or a common search space, e.g. configured with multicast and/orbroadcast signaling. A control region may span one or more block symbolsand/or allocation units and/or have an extension in frequency domaincorresponding to a control region bandwidth and/or a plurality ofsubcarriers or resource blocks, e.g. physical and/or virtual resourceblocks. It should be noted that control signaling of the set of controlsignalings may comprise control signaling that may occupy time/frequencyresource/s (e.g., a set of resources) included in the control regionand/or search space, but do not necessarily have to use all resources ofthe control region and/or search space. In general, the control regionand/or search space may represent resources (e.g., a set oftime/frequency resources) a receiver may monitor and/or search forcontrol signaling, e.g. control signaling addressed to and/or intendedfor the receiver. Parameters and/or characteristics of the search spacemay limit and/or define the monitoring in more detail.

In general, a symbol or allocation unit may represent and/or beassociated to a symbol time length (or unit time length), which may bedependent on the carrier and/or subcarrier spacing and/or numerology ofthe associated carrier. Accordingly, a symbol may be considered toindicate a time interval having a symbol time length in relation tofrequency domain. A symbol time length may be dependent on a carrierfrequency and/or bandwidth and/or numerology and/or subcarrier spacingof, or associated to, a symbol. Accordingly, different symbols may havedifferent symbol time lengths. In particular, numerologies withdifferent subcarrier spacings may have different symbol time length.Generally, a symbol time length may be based on, and/or include, a guardtime interval or cyclic extension, e.g. prefix or postfix.

A sidelink may generally represent a communication channel (or channelstructure) between two UEs and/or terminals, in which data istransmitted between the participants (UEs and/or terminals) via thecommunication channel, e.g. directly and/or without being relayed via anetwork node. A sidelink may be established only and/or directly via airinterface/s of the participant, which may be directly linked via thesidelink communication channel. In some variants, sidelink communicationmay be performed without interaction by a network node, e.g. on fixedlydefined resources and/or on resources negotiated between theparticipants. Alternatively, or additionally, it may be considered thata network node provides some control functionality, e.g. by configuringresources, in particular one or more resource pool/s, for sidelinkcommunication, and/or monitoring a sidelink, e.g. for charging purposes.

Sidelink communication may also be referred to as device-to-device (D2D)communication, and/or in some cases as ProSe (Proximity Services)communication, e.g. in the context of LTE. A sidelink may be implementedin the context of V2x communication (Vehicular communication), e.g. V2V(Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure) and/or V2P(Vehicle-to-Person). Any device adapted for sidelink communication maybe considered a user equipment or terminal.

A sidelink communication channel (or structure) may comprise one or more(e.g., physical or logical) channels, e.g. a PSCCH (Physical SidelinkControl CHannel, which may for example carry control information like anacknowledgement position indication, and/or a PSSCH (Physical SidelinkShared CHannel, which for example may carry data and/or acknowledgementsignaling). It may be considered that a sidelink communication channel(or structure) pertains to and/or used one or more carrier/s and/orfrequency range/s associated to, and/or being used by, cellularcommunication, e.g. according to a specific license and/or standard.Participants may share a (physical) channel and/or resources, inparticular in frequency domain and/or related to a frequency resourcelike a carrier) of a sidelink, such that two or more participantstransmit thereon, e.g. simultaneously, and/or time-shifted, and/or theremay be associated specific channels and/or resources to specificparticipants, so that for example only one participant transmits on aspecific channel or on a specific resource or specific resources, e.g.,in frequency domain and/or related to one or more carriers orsubcarriers.

A sidelink may comply with, and/or be implemented according to, aspecific standard, e.g. an LTE-based standard and/or NR. A sidelink mayutilise TDD (Time Division Duplex) and/or FDD (Frequency DivisionDuplex) technology, e.g. as configured by a network node, and/orpreconfigured and/or negotiated between the participants. A userequipment may be considered to be adapted for sidelink communication ifit, and/or its radio circuitry and/or processing circuitry, is adaptedfor utilising a sidelink, e.g. on one or more frequency ranges and/orcarriers and/or in one or more formats, in particular according to aspecific standard. It may be generally considered that a Radio AccessNetwork is defined by two participants of a sidelink communication.

Alternatively, or additionally, a Radio Access Network may berepresented, and/or defined with, and/or be related to a network nodeand/or communication with such a node.

Communication or communicating may generally comprise transmittingand/or receiving signaling. Communication on a sidelink (or sidelinksignaling) may comprise utilising the sidelink for communication(respectively, for signaling). Sidelink transmission and/or transmittingon a sidelink may be considered to comprise transmission utilising thesidelink, e.g. associated resources and/or transmission formats and/orcircuitry and/or the air interface. Sidelink reception and/or receivingon a sidelink may be considered to comprise reception utilising thesidelink, e.g. associated resources and/or transmission formats and/orcircuitry and/or the air interface. Sidelink control information (e.g.,SCI) may generally be considered to comprise control informationtransmitted utilising a sidelink.

Generally, carrier aggregation (CA) may refer to the concept of a radioconnection and/or communication link between a wireless and/or cellularcommunication network and/or network node and a terminal or on asidelink comprising a plurality of carriers for at least one directionof transmission (e.g. DL and/or UL), as well as to the aggregate ofcarriers. A corresponding communication link may be referred to ascarrier aggregated communication link or CA communication link; carriersin a carrier aggregate may be referred to as component carriers (CC). Insuch a link, data may be transmitted over more than one of the carriersand/or all the carriers of the carrier aggregation (the aggregate ofcarriers). A carrier aggregation may comprise one (or more) dedicatedcontrol carriers and/or primary carriers (which may e.g. be referred toas primary component carrier or PCC), over which control information maybe transmitted, wherein the control information may refer to the primarycarrier and other carriers, which may be referred to as secondarycarriers (or secondary component carrier, SCC). However, in someapproaches, control information may be sent over more than one carrierof an aggregate, e.g. one or more PCCs and one PCC and one or more SCCs.

A transmission may generally pertain to a specific channel and/orspecific resources, in particular with a starting symbol and endingsymbol in time, covering the interval therebetween. A scheduledtransmission may be a transmission scheduled and/or expected and/or forwhich resources are scheduled or provided or reserved. However, notevery scheduled transmission has to be realized. For example, ascheduled downlink transmission may not be received, or a scheduleduplink transmission may not be transmitted due to power limitations, orother influences (e.g., a channel on an unlicensed carrier beingoccupied). A transmission may be scheduled for a transmission timingsubstructure (e.g., a mini-slot, and/or covering only a part of atransmission timing structure) within a transmission timing structurelike a slot. A border symbol may be indicative of a symbol in thetransmission timing structure at which the transmission starts or ends.

Predefined in the context of this disclosure may refer to the relatedinformation being defined for example in a standard, and/or beingavailable without specific configuration from a network or network node,e.g. stored in memory, for example independent of being configured.Configured or configurable may be considered to pertain to thecorresponding information being set/configured, e.g. by the network or anetwork node.

A configuration or schedule, like a mini-slot configuration and/orstructure configuration, may schedule transmissions, e.g. for thetime/transmissions it is valid, and/or transmissions may be scheduled byseparate signaling or separate configuration, e.g. separate RRCsignaling and/or downlink control information signaling. Thetransmission/s scheduled may represent signaling to be transmitted bythe device for which it is scheduled, or signaling to be received by thedevice for which it is scheduled, depending on which side of acommunication the device is. It should be noted that downlink controlinformation or specifically DCI signaling may be considered physicallayer signaling, in contrast to higher layer signaling like MAC (MediumAccess Control) signaling or RRC layer signaling. The higher the layerof signaling is, the less frequent/the more time/resource consuming itmay be considered, at least partially due to the information containedin such signaling having to be passed on through several layers, eachlayer requiring processing and handling.

A scheduled transmission, and/or transmission timing structure like amini-slot or slot, may pertain to a specific channel, in particular aphysical uplink shared channel, a physical uplink control channel, or aphysical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and/or maypertain to a specific cell and/or carrier aggregation. A correspondingconfiguration, e.g. scheduling configuration or symbol configuration maypertain to such channel, cell and/or carrier aggregation. It may beconsidered that the scheduled transmission represents transmission on aphysical channel, in particular a shared physical channel, for example aphysical uplink shared channel or physical downlink shared channel. Forsuch channels, semi-persistent configuring may be particularly suitable.

Generally, a configuration may be a configuration indicating timing,and/or be represented or configured with corresponding configurationdata. A configuration may be embedded in, and/or comprised in, a messageor configuration or corresponding data, which may indicate and/orschedule resources, in particular semi-persistently and/orsemi-statically.

A control region of a transmission timing structure may be an intervalin time and/or frequency domain for intended or scheduled or reservedfor control signaling, in particular downlink control signaling, and/orfor a specific control channel, e.g. a physical downlink control channellike PDCCH. The interval may comprise, and/or consist of, a number ofsymbols in time, which may be configured or configurable, e.g. by(UE-specific) dedicated signaling (which may be single-cast, for exampleaddressed to or intended for a specific UE), e.g. on a PDCCH, or RRCsignaling, or on a multicast or broadcast channel. In general, thetransmission timing structure may comprise a control region covering aconfigurable number of symbols. It may be considered that in general theborder symbol is configured to be after the control region in time. Acontrol region may be associated, e.g. via configuration and/ordetermination, to one or more specific UEs and/or formats of PDCCHand/or DCI and/or identifiers, e.g. UE identifiers and/or RNTIs orcarrier/cell identifiers, and/or be represented and/or associated to aCORESET and/or a search space.

The duration of a symbol (symbol time length or interval or allocationunit) of the transmission timing structure may generally be dependent ona numerology and/or carrier, wherein the numerology and/or carrier maybe configurable. The numerology may be the numerology to be used for thescheduled transmission.

A transmission timing structure may comprise a plurality of allocationunits or symbols, and/or define an interval comprising several symbolsor allocation units (respectively their associated time intervals). Inthe context of this disclosure, it should be noted that a reference to asymbol for ease of reference may be interpreted to refer to the timedomain projection or time interval or time component or duration orlength in time of the symbol, unless it is clear from the context thatthe frequency domain component also has to be considered. Examples oftransmission timing structures include slot, subframe, mini-slot (whichalso may be considered a substructure of a slot), slot aggregation(which may comprise a plurality of slots and may be considered asuperstructure of a slot), respectively their time domain component. Atransmission timing structure may generally comprise a plurality ofsymbols and/or allocation units defining the time domain extension(e.g., interval or length or duration) of the transmission timingstructure, and arranged neighboring to each other in a numberedsequence. A timing structure (which may also be considered orimplemented as synchronisation structure) may be defined by a successionof such transmission timing structures, which may for example define atiming grid with symbols representing the smallest grid structures. Atransmission timing structure, and/or a border symbol or a scheduledtransmission may be determined or scheduled in relation to such a timinggrid. A transmission timing structure of reception may be thetransmission timing structure in which the scheduling control signalingis received, e.g. in relation to the timing grid. A transmission timingstructure may in particular be a slot or subframe or in some cases, amini-slot. In some cases, a timing structure may be represented by aframe structure. Timing structures may be associated to specifictransmitters and/or cells and/or beams and/or signalings.

Feedback signaling may be considered a form or control signaling, e.g.uplink or sidelink control signaling, like UCI (Uplink ControlInformation) signaling or SCI (Sidelink Control Information) signaling.Feedback signaling may in particular comprise and/or representacknowledgement signaling and/or acknowledgement information and/ormeasurement reporting.

Signaling utilising, and/or on and/or associated to, resources or aresource structure may be signaling covering the resources or structure,signaling on the associated frequency/ies and/or in the associated timeinterval/s. It may be considered that a signaling resource structurecomprises and/or encompasses one or more substructures, which may beassociated to one or more different channels and/or types of signalingand/or comprise one or more holes (resource element/s not scheduled fortransmissions or reception of transmissions). A resource substructure,e.g. a feedback resource structure, may generally be continuous in timeand/or frequency, within the associated intervals. It may be consideredthat a substructure, in particular a feedback resource structure,represents a rectangle filled with one or more resource elements intime/frequency space. However, in some cases, a resource structure orsubstructure, in particular a frequency resource range, may represent anon-continuous pattern of resources in one or more domains, e.g. timeand/or frequency. The resource elements of a substructure may bescheduled for associated signaling.

Example types of signaling comprise signaling of a specificcommunication direction, in particular, uplink signaling, downlinksignaling, sidelink signaling, as well as reference signaling (e.g., SRSor CRS or CSI-RS), communication signaling, control signaling, and/orsignaling associated to a specific channel like PUSCH, PDSCH, PUCCH,PDCCH, PSCCH, PSSCH, etc.).

In some cases, a shifting object like a signaling or signals orsequences or information may be shifted, e.g. relative to a predecessor(e.g., one is subject to a shift, and the shifted version is used), orrelative to another (e.g., one associated to one signaling or allocationunit may be shifted to another associated to a second signaling orallocation unit, both may be used). One possible way of shifting isoperating a code on it, e.g. to multiply each element of a shiftingobject with a factor. A ramping (e.g. multiplying with a monotonouslyincreasing or periodic factor) may be considered an example of shifting.Another is a cyclic shift in a domain or interval. A cyclic shift (orcircular shift) may correspond to a rearrangement of the elements in theshifting object, corresponding to moving the final element or elementsto the first position, while shifting all other entries to the nextposition, or by performing the inverse operation (such that the shiftedobject as the result will have the same elements as the shifting object,in a shifted but similar order). Shifting in general may be specific toan interval in a domain, e.g. an allocation unit in time domain, or abandwidth in frequency domain. For example, it may be considered thatsignals or modulation symbols in an allocation unit are shifted, suchthat the order of the modulation symbols or signals is shifted in theallocation unit. In another example, allocation units may be shifted,e.g. in a larger time interval—this may leave signals in the allocationunits unshifted with reference to the individual allocation unit, butmay change the order of the allocation units. Domains for shifting mayfor example be time domain and/or phase domain and/or frequency domain.Multiple shifts in the same domain or different domains, and/or the sameinterval or different intervals (differently sized intervals, forexample) may be performed.

A transmitting radio node may in some variants be represented by, and/orconsidered or implemented as, a signaling radio node. A receiving radionode in some variants may be represented by, and/or considered orimplemented as, feedback radio node.

Synchronisation signaling may be provided by a transmitting (radio)node, e.g. a network node, to allow a receiving (radio) node like a userequipment to identify a cell and/or transmitter, and/or to synchroniseto the transmitter and/or cell, and/or to provide information regardingthe transmitter and/or cell. Synchronisation signaling may in generalcomprise one or more components (e.g., different types of signaling),e.g. primary synchronisation signaling (PSS) and/or secondarysynchronisation signaling (SSS) and/or broadcast signaling and/or systeminformation (e.g., on a Physical Broadcast Channel). System information(SI) may for example comprise a Master Information Block (MIB) and/orone or more System Information Blocks (SIBs), e.g. at least a SIB1. Thedifferent components may be transmitted in a block, e.g. neighboring intime and/or frequency domain. PSS may indicate a transmitter and/or cellidentity, e.g. a group of cell and/or transmitter identities the cellbelongs to. The SSS may indicate which cell and/or transmitter of thegroup the cell and/or transmitter the transmitter is associated toand/or represented by (it may be considered that more than onetransmitters are associated to the same ID, e.g. in the same cell and/orin a multiple transmission point scenario). PSS may indicate a roughertiming (larger granularity) than the SSS; synchronisation may be basedon evaluating PSS and SSS, e.g. in sequence and/or step-wise from afirst (rougher) timing to a second (finer) timing. Synchronisationsignaling, e.g. PSS and/or SSS, and/or SI may indicate a beam (e.g.,beam ID and/or number) and/or beam timing of a beam used fortransmitting the synchronisation signaling. Synchronisation signalingmay be in form of a SS/PBCH block and/or SSB. It may be considered thatsynchronisation signaling is transmitted periodically, e.g. every NP ms,e.g. NP=20, 40 or 80. In some cases, synchronisation signaling may betransmitted in bursts, e.g. such that signaling is repeated over morethan one synchronisation time interval (e.g., neighboring timeintervals, or with gaps between them); a burst may be associated to aburst interval, e.g. within a slot and/or frame and/or a number of NBallocation units, wherein NB may be 100 or less, or 50 or less, or 40 orless or 20 or less. In some cases, a synchronisation time interval maycomprise NS allocation units carrying signaling (e.g., PSS and/or SSSand/or PBCH or SI); it may be considered that a burst interval comprisesP1 (P1>=1) occasions (thus, P1-1 repetitions) of the synchronisationsignaling, and/or comprises at least P1×NS allocation units in timedomain; it may be larger than P1×NS units, e.g. to allow for gapsbetween individual occasions and/or one or more guard interval/s. Insome variants, it may comprise at least (P1+1)×NS allocation units, or(P1+2)×NS allocation units, e.g. including gaps between occasions. Thesynchronisation signaling may be transmitted on, and/or be associatedto, a synchronisation bandwidth in frequency space, which may bepredefined and/or configured or configurable (e.g., for a receivingnode). The synchronisation bandwidth may for example be 100 MHz and/or500 MHz, or 250 MHz, or another value. A synchronisation bandwidth maybe associated to and/or be arranged within a carrier and/or acommunication frequency interval. It may be considered that for eachcarrier and/or frequency interval, there are one or more possiblelocation of a synchronisation bandwidth. PSS and/or SSS may beconsidered physical layer signaling representing information withouthaving coding (e.g., error coding). Broadcast signaling, e.g. on a PBCHmay be coded, in particular comprises error coding like error correctioncoding, e.g. a CRC.

In the context of this disclosure, there may be distinguished betweendynamically scheduled or aperiodic transmission and/or configuration,and semi-static or semi-persistent or periodic transmission and/orconfiguration. The term “dynamic” or similar terms may generally pertainto configuration/transmission valid and/or scheduled and/or configuredfor (relatively) short timescales and/or a (e.g., predefined and/orconfigured and/or limited and/or definite) number of occurrences and/ortransmission timing structures, e.g. one or more transmission timingstructures like slots or slot aggregations, and/or for one or more(e.g., specific number) of transmission/occurrences. Dynamicconfiguration may be based on low-level signaling, e.g. controlsignaling on the physical layer and/or MAC layer, in particular in theform of DCI or SCI. Periodic/semi-static may pertain to longertimescales, e.g. several slots and/or more than one frame, and/or anon-defined number of occurrences, e.g., until a dynamic configurationcontradicts, or until a new periodic configuration arrives. A periodicor semi-static configuration may be based on, and/or be configured with,higher-layer signaling, in particular RCL layer signaling and/or RRCsignaling and/or MAC signaling.

In this disclosure, for purposes of explanation and not limitation,specific details are set forth (such as particular network functions,processes and signaling steps) in order to provide a thoroughunderstanding of the technique presented herein. It will be apparent toone skilled in the art that the present concepts and aspects may bepracticed in other variants and variants that depart from these specificdetails.

For example, the concepts and variants are partially described in thecontext of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or NewRadio mobile or wireless communications technologies; however, this doesnot rule out the use of the present concepts and aspects in connectionwith additional or alternative mobile communication technologies such asthe Global System for Mobile Communications (GSM) or IEEE standards asIEEE 802.11ad or IEEE 802.11 ay. While described variants may pertain tocertain Technical Specifications (TSs) of the Third GenerationPartnership Project (3GPP), it will be appreciated that the presentapproaches, concepts and aspects could also be realized in connectionwith different Performance Management (PM) specifications.

Moreover, those skilled in the art will appreciate that the services,functions and steps explained herein may be implemented using softwarefunctioning in conjunction with a programmed microprocessor, or using anApplication Specific Integrated Circuit (ASIC), a Digital SignalProcessor (DSP), a Field Programmable Gate Array (FPGA) or generalpurpose computer. It will also be appreciated that while the variantsdescribed herein are elucidated in the context of methods and devices,the concepts and aspects presented herein may also be embodied in aprogram product as well as in a system comprising control circuitry,e.g. a computer processor and a memory coupled to the processor, whereinthe memory is encoded with one or more programs or program products thatexecute the services, functions and steps disclosed herein.

It is believed that the advantages of the aspects and variants presentedherein will be fully understood from the foregoing description, and itwill be apparent that various changes may be made in the form,constructions and arrangement of the exemplary aspects thereof withoutdeparting from the scope of the concepts and aspects described herein orwithout sacrificing all of its advantageous effects. The aspectspresented herein can be varied in many ways.

Some useful abbreviations comprise

Abbreviation Explanation ACK/NACK Acknowledgment/NegativeAcknowledgement ARQ Automatic Repeat reQuest BER Bit Error Rate BLERBlock Error Rate BPSK Binary Phase Shift Keying BWP Bandwidth Part CAZACConstant Amplitude Zero Cross Correlation CB Code Block CBB Code BlockBundle CBG Code Block Group CBGFI CBG Flush Indication (indicatingwhether to perform Soft Combining) CBGTI CBG Transmission InformationCDM Code Division Multiplex CM Cubic Metric CORESET Control Resource SetCQI Channel Quality Information CRC Cyclic Redundancy Check CRS Commonreference signal CSI Channel State Information CSI-RS Channel stateinformation reference signal DAI Downlink Assignment Indicator DCIDownlink Control Information DFT Discrete Fourier Transform DFTS-FDMDFT-spread-FDM DM(-)RS Demodulation reference signal(ing) eMBB enhancedMobile BroadBand FDD Frequency Division Duplex FDE Frequency DomainEqualisation FDF Frequency Domain Filtering FDM Frequency DivisionMultiplex HARQ Hybrid Automatic Repeat Request IAB Integrated Access andBackhaul IFFT Inverse Fast Fourier Transform IR Impulse Response ISIInter Symbol Interference MBB Mobile Broadband MCS Modulation and CodingScheme MIMO Multiple-input-multiple-output MRC Maximum-ratio combiningMRT Maximum-ratio transmission MU-MIMO Multiusermultiple-input-multiple-output OFDM/A Orthogonal Frequency DivisionMultiplex/Multiple Access PAPR Peak to Average Power Ratio PDCCHPhysical Downlink Control Channel PDSCH Physical Downlink Shared ChannelPRACH Physical Random Access CHannel PRB Physical Resource Block PUCCHPhysical Uplink Control Channel PUSCH Physical Uplink Shared Channel(P)SCCH (Physical) Sidelink Control Channel PSS Primary SynchronisationSignal(ing) PT-RS Phase Tracking Reference Signaling (P)SSCH (Physical)Sidelink Shared Channel QAM Quadrature Amplitude Modulation OCCOrthogonal Cover Code QPSK Quadrature Phase Shift Keying PSD PowerSpectral Density RAN Radio Access Network RAT Radio Access Technology RBResource Block RNTI Radio Network Temporary Identifier RRC RadioResource Control RX Receiver, Reception, Reception-related/side SAScheduling Assignment SC-FDE Single Carrier Frequency DomainEqualisation SC-FDM/A Single Carrier Frequency DivisionMultiplex/Multiple Access SCI Sidelink Control Information SINRSignal-to-interference-plus-noise ratio SIR Signal-to-interference ratioSNR Signal-to-noise-ratio SR Scheduling Request SRS Sounding ReferenceSignal(ing) SSS Secondary Synchronisation Signal(ing) SVD Singular-valuedecomposition TB Transport Block TDD Time Division Duplex TDM TimeDivision Multiplex T-RS Tracking Reference Signaling or Timing ReferenceSignaling TX Transmitter, Transmission, Transmission-related/side UCIUplink Control Information UE User Equipment URLLC Ultra Low LatencyHigh Reliability Communication VL-MIMO Very-largemultiple-input-multiple-output ZF Zero Forcing ZP Zero-Power, e.g. mutedCSI-RS symbol

Abbreviations may be considered to follow 3G PP usage if applicable.

1. A method of operating a receiving radio node in a wirelesscommunication network, the method comprising: communicating utilisingdata signaling based on a received control information message, thecontrol information message scheduling multiple occurrences of datasignaling, the communicating being based on extracting a code blockgroup (CBG) setup for communicating based on at least one of thereceived control information message and a CBG configuration.
 2. Areceiving radio node for a wireless communication network, the receivingradio node configured to: communicate utilising data signaling based ona received control information message, the control information messagescheduling multiple occurrences of data signaling, the communicatingbeing based on extracting a code block group (CBG) setup forcommunicating based on at least one of the received control informationmessage and a CBG configuration.
 3. A method of operating a signalingradio node in a wireless communication network, the method comprising:communicating, with a receiving radio node, utilising data signaling,the communicating being according to a code block group (CBG) setupindicated to the receiving radio node with at least one of a controlinformation message scheduling multiple occurrences of data signalingand a CBG configuration.
 4. A signaling radio node for a wirelesscommunication network, the signaling radio node configured to:communicate, with a receiving radio node, utilising data signaling, thecommunicating being according to a code block group (CBG) setupindicated to the receiving radio node with at least one of a controlinformation message scheduling multiple occurrences of data signalingand a CBG configuration.
 5. The method according to claim 1, wherein thedata signaling is on a physical uplink data channel or a physicaldownlink data channel.
 6. The method according to claim 1, wherein themultiple occurrences of data signaling are associated to differenttransmission resources.
 7. Program product A computer storage mediumstoring a computer program comprising instructions that, when executed,cause processing circuitry to at least one of control and perform amethod comprising: communicating utilising data signaling based on areceived control information message, the control information messagescheduling multiple occurrences of data signaling, the communicatingbeing based on extracting a code block group (CBG) setup forcommunicating based on at least one of the received control informationmessage and a CBG configuration.
 8. (canceled)
 9. The receiving radionode according to claim 2, wherein the data signaling is on one of aphysical uplink data channel and a physical downlink data channel. 10.The receiving radio node according to claim 9, wherein the multipleoccurrences of data signaling are associated to different transmissionresources.
 11. The receiving radio node according to claim 2, whereinthe multiple occurrences of data signaling are associated to differenttransmission resources.
 12. The method according to claim 3, wherein thedata signaling is on one of a physical uplink data channel and aphysical downlink data channel.
 13. The method according to claim 12,wherein the multiple occurrences of data signaling are associated todifferent transmission resources.
 14. The method according to claim 3,wherein the multiple occurrences of data signaling are associated todifferent transmission resources.
 15. The signaling radio node accordingto claim 4, wherein the data signaling is on one of a physical uplinkdata channel and a physical downlink data channel.
 16. The signalingradio node according to claim 15, wherein the multiple occurrences ofdata signaling are associated to different transmission resources. 17.The signaling radio node according to claim 4, wherein the multipleoccurrences of data signaling are associated to different transmissionresources.
 18. The method according to claim 5, wherein the multipleoccurrences of data signaling are associated to different transmissionresources.